Ability for maintainers to update own ports

Kris Kennaway kris at obsecurity.org
Tue Nov 11 14:36:36 PST 2003

On Tue, Nov 11, 2003 at 05:12:47PM -0500, Charles Swiger wrote:

> If someone could do a "cvs checkout -r RELENG_4_5" against the ports 
> CVS repo, and update to the latest version of each port which is known 
> to build on their version of the OS, that user would obtain 
> significantly more benefit than being told that they need to upgrade 
> their OS in order to use newer port versions.

I think you're missing the point.  No-one disagrees that it would be
wonderful if users of old releases could continue to use up-to-date

The problem is that making that work requires a *lot* of effort, and
there just isn't any to spare from the ranks of the people who are
currently doing the bulk of the work to keep the Ports Collection
useful and relevant, given that it's already a continual uphill
struggle to keep up with the growth of the ports collection and the
demands placed on it by freebsd (support for new architectures, new
releases - soon we'll have 3 branches to support, etc).

You just can't ignore this by pointing out that the goal is
worthwhile: any major change that puts a significant extra burden on
existing contributors is essentially a non-starter.

If you think the Ports Collection should maintain certain higher
standards with respect to supporting old releases, you personally are
going to have to put in the effort to ensure that it comes to pass.

That means keeping a testbed of systems for testing whatever
combinations of OS and software you want to support, and putting in
the effort on a long-term basis to support this.  If you can show that
you (and any other interested parties) are going to stick with this
for a reasonable term, then we can talk about what we (FreeBSD) can do
to support your efforts.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20031111/cca8e495/attachment.bin

More information about the freebsd-ports mailing list