Date: Wed, 11 Aug 2004 12:38:37 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Oliver Eikemeier <eikemeier@fillmore-labs.com> Cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: CVSROOT modules ports/shells Makefilepkg-install patch-bashline.c patch-builtins_shopt.def patch-config-bot.h ... Message-ID: <1092242317.731.26.camel@gyros> In-Reply-To: <8C6EA0DC-EBB4-11D8-887A-00039312D914@fillmore-labs.com> References: <8C6EA0DC-EBB4-11D8-887A-00039312D914@fillmore-labs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-pJ4QuQkD0LjOQDC8Bd9j Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-08-11 at 12:36, Oliver Eikemeier wrote: > Joe Marcus Clarke wrote: >=20 > >> When you think repocopying bash3 -> bash is > >> a good idea, just do it. > > [...] > > Just file the PR, and the copy will be done. >=20 > Difficult to decide: >=20 > I believe we have a valid reason to have openldap21 and openldap22 in=20 > the tree, like bash2 and bash3 or apache13 and apache2. I already took=20 > care of deleting openldap1 and openldap20, and we could do the same with=20 > bash1 (and probably security/cyrus-sasl (which is an old 1.5 version,=20 > used only by very few ports)). >=20 > Do we have an rationale which port should be in what directory? E.g. `no=20 > number -> current release', `number -> development or old version' or=20 > some other scheme? And how do we fit libxml/libxml2 into the pattern? The libxml/libxml2 thing was purely module name-related. Libxml was the beginning, and when they needed a new API, they released a libxml2 module. Honestly, I don't know why we have a bash1 as opposed to just bash, but there was another instance with gimp1. Since then, though, gimp1 was canned, and now we just have gimp. That said, I prefer the non-versioned base port. Joe >=20 > -Oliver --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-pJ4QuQkD0LjOQDC8Bd9j Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQBBGkuNb2iPiv4Uz4cRAjlPAJ9Rsoe7tbRlLEg0EBEo3bUhBARl5wCeO4qU ZYpiTmhF8NuWJW4yVUIsQGo= =DUHQ -----END PGP SIGNATURE----- --=-pJ4QuQkD0LjOQDC8Bd9j--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1092242317.731.26.camel>