[Bug 214070] www/firefox and other mozilla ports: split release candidates off into firefox-devel

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Nov 2 18:18:00 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214070

            Bug ID: 214070
           Summary: www/firefox and other mozilla ports: split release
                    candidates off into firefox-devel
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: gecko at FreeBSD.org
          Reporter: la5lbtyi at aon.at
          Assignee: gecko at FreeBSD.org
             Flags: maintainer-feedback?(gecko at FreeBSD.org)

This is a change request.

I am using portmaster to update my installed ports.

Since some time, mozilla ports (firefox, libxul, thunderbird) are updated
taking release candidates into account. While this has the advantage of quickly
exposing new features to the general public, it also means that potentially
unstable code is being distributed. Furthermore, this is done in a rather
intransparent way, as one cannot deduce from the version designation that a
release candidate has actually been installed. For example, today's update
creates firefox-50.0,1 from
firefox/candidates/50.0-candidates/build1/source/firefox-50.0.source.tar.xz and
libxul-45.5.0 from
firefox/candidates/45.5.0esr-candidates/build1/source/firefox-45.5.0esr.source.tar.xz.
A further disadvantage is the rapid succession of new releases with little
relevant changes requiring frequent updates.

I therefore propose to split off -devel versions of these ports where users who
want to stay on the bleeding edge are served the release candidates as is
currently done on the main ports. The main ports themselves should revert to
only upgrading to truly released versions.

-- Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list