Date: Fri, 22 Mar 1996 17:03:27 -0800 From: asami@cs.berkeley.edu (Satoshi Asami) To: adam@veda.is Cc: andreas@knobel.gun.de, freebsd-ports@freebsd.org Subject: Re: Update for wn port (because of new wn release) Message-ID: <199603230103.RAA10937@sunrise.cs.berkeley.edu> In-Reply-To: <199603201127.LAA14771@veda.is> (message from Adam David on Wed, 20 Mar 1996 11:27:01 %2B0000 (GMT))
next in thread | previous in thread | raw e-mail | index | archive | help
* 1.12.5 has been replaced by 1.12.6 as the latest stable version, whereas * 1.13.3 is the latest current version. This raises the question, which I have * been meaning to ask for some time on the freebsd-ports mailing list, about * general guidelines for maintaining 2 versions of a port (as in this case) * corresponding to -current and -stable. If it works well enough, just overwrite the old one, if it doesn't work very well, it shouldn't go in. In general, I think we should avoid cluttering up the ports tree with separate versions of the same port, it's already quite big as it is. ;) There are exceptions to this of course, like incompatible versions where the old one is still widely used (tcl/tk is a prime example). Well, if you (the porter) is willing to maintain both versions, I'm not to discourage that, of course. * freefall. But even if that was the case, it has been many months now since * general committers/porters have not had write access to this directory. Yes. There has been just too many instances where we got legally questionable stuff up there due to someone's carelessness. Since ftp.freebsd.org is mirrored from all over the world, we decided it is too risky to take a chance. * Again, I assumed (probably wrongly) that there was a regular script running * under cron to do a "make fetch" in /usr/ports for the purpose of repopulating * the ftp archive distfiles. The write permission of freefall's /usr/ports/distfiles was turned off at the same time for the same reason (because this directory is distributed by sup). The sup on wcarchive is turned off because we intend to keep old versions (particularly the ones that correspond to the most recent release) on wcarchive but not on freefall. * I doubt whether we have write access to the ftp distfiles directory. This * seems to be Satoshi's exclusive domain. Is the accepted procedure therefore * to upload to an incoming directory and notify asami@freebsd.org of the new * file(s)? If there's something missing, just let me know, and I'll put it up. Some old things have disappeared before I realized that wcarchive's distfiles directory was modified by sup, but I've been keeping track of most recent stuff. In general, this is what happens. When I see a commit message for a new port or an upgrade, I build the package (this is when you see me tweaking Makefiles and PLISTs and such) on thud and copy the distfile to freefall and wcarchive. If it's an upgrade, the old version's distfile is deleted from freefall, and from wcarchive too if the old version wasn't the one in ports-2.1. Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603230103.RAA10937>