Date: Mon, 11 Mar 2002 14:33:42 +0100 From: Stijn Hoop <stijn@win.tue.nl> To: Sue Blake <sue@welearn.com.au> Cc: "Simon 'corecode' Schubert" <corecode@corecode.ath.cx>, freebsd-ports@freebsd.org Subject: Re: handling static filenames Message-ID: <20020311143342.F60503@pcwin002.win.tue.nl> In-Reply-To: <20020312002733.J16874@welearn.com.au>; from sue@welearn.com.au on Tue, Mar 12, 2002 at 12:27:33AM %2B1100 References: <20020311225125.B96107@welearn.com.au> <20020311132113.5dd83daf.corecode@corecode.ath.cx> <20020312002733.J16874@welearn.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
--fOHHtNG4YXGJ0yqR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi,
On Tue, Mar 12, 2002 at 12:27:33AM +1100, Sue Blake wrote:
> On Mon, Mar 11, 2002 at 01:21:13PM +0100, Simon 'corecode' Schubert wrote:
> > On Mon, 11 Mar 2002 22:51:25 +1100 Sue Blake <sue@welearn.com.au> wrote:
> >=20
> > > I'm working on four ports (2 down, 2 to go) that have source archives
> > > which do not change name when they are upgraded. How do we deal with
> > > this? Keep a copy of foo.zip somewhere else, renamed to foo-1.23.zip
> > > and list it in the Makefile instead of or as well as the author's
> > > site? I could plonk them under people.freebsd.org but I don't know
> > > that it's the right way to handle the situation. Do we have any
> > > precedents or battle scars?
> >=20
> > if you look at other ports which handle this:
> > they just do a
> >=20
> > DISTNAME=3D ${PORTNAME}
> >=20
> > or similar.
>=20
> Thanks, but it was more the users' problems that I was concerned about.
> What happens when http://www.foo.com/foo.zip changes slightly two weeks a=
fter
> the port is out, BUT the filename is the same?
> 1. The properly downloaded source file will be unusable with the port.
Yes, but the port will not proceed to compile because the distinfo is
mismatched.
> 2. The reason for the problem and its solution will not be obvious to the
> user.
Well, users will not be able to build the port due to an MD5 mismatch. They=
'll
probably then proceed to bug the maintainer, and/or the lists.
> 3. There is no way to get the older file.
That's a consequence of these filenames.
> 4. It is not obvious that a later port might work with the current file.
It won't (at least, not unless you, as the port maintainer, request
that the MD5 will be ignored).
> 5. If the author fixes his doc typos every Sunday for a few weeks, it'll
> be a nightmare to keep up to date, and no chance of a satisfactory
> "last month" version being used since the source archive is
> (a) indistinguishable, and (b) not available from the site.
Yes. This is again a consequence of these filenames.
The only proper solution is to politely ask the upstream release manager
to label their distributions, and keep older versions online. This isn't
hard to do on their part, and is less confusing for *all* their users, not
just the FreeBSD ones.
--Stijn
--=20
] Nothing safer than a 'cat /dev/wallet | grep $price > real-person; \
] mv $thing-to-buy $my-case
I'd prefer 'mv $thing-to-buy $my-case && cat /dev/wallet | \
grep $price > real-person
-- Anonymous, freebsd-questions@freebsd.org,
in message <200108020628.IAA11775@hugo10.ka.punkt.de>
--fOHHtNG4YXGJ0yqR
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE8jLI2Y3r/tLQmfWcRAk1VAKCliQ4p8Fnd8RWurff17dMf4+7QMwCgk+AM
9RVjjd0xYkhOkmzEGHx3pWo=
=b8Kj
-----END PGP SIGNATURE-----
--fOHHtNG4YXGJ0yqR--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020311143342.F60503>