cvs commit: CVSROOT modules ports/shells Makefilepkg-install patch-bashline.c patch-builtins_shopt.def patch-config-bot.h ...

Joe Marcus Clarke marcus at marcuscom.com
Wed Aug 11 09:40:00 PDT 2004


On Wed, 2004-08-11 at 12:36, Oliver Eikemeier wrote:
> Joe Marcus Clarke wrote:
> 
> >>  When you think repocopying bash3 -> bash is
> >> a good idea, just do it.
> > [...]
> > Just file the PR, and the copy will be done.
> 
> Difficult to decide:
> 
> I believe we have a valid reason to have openldap21 and openldap22 in 
> the tree, like bash2 and bash3 or apache13 and apache2. I already took 
> care of deleting openldap1 and openldap20, and we could do the same with 
> bash1 (and probably security/cyrus-sasl (which is an old 1.5 version, 
> used only by very few ports)).
> 
> Do we have an rationale which port should be in what directory? E.g. `no 
> number -> current release', `number -> development or old version' or 
> 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

> 
> -Oliver
-- 
PGP Key : http://www.marcuscom.com/pgp.asc


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/cvs-all/attachments/20040811/3b14bcc5/attachment.bin


More information about the cvs-all mailing list