Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 08 Jul 1999 15:00:24 +0200
From:      Marcel Moolenaar <marcel@scc.nl>
To:        Sheldon Hearn <sheldonh@uunet.co.za>
Cc:        cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: ports/emulators/linux-base-5.2 - Imported sources
Message-ID:  <3784A0E8.C0394E82@scc.nl>
References:  <7533.931436892@axl.noc.iafrica.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Sheldon Hearn wrote:
> 
> On Thu, 08 Jul 1999 14:10:38 +0200, Marcel Moolenaar wrote:
> 
> > The reasons I see are:
> > 1) The directory is named the same as the port
> 
> This is a terrible reason.

Oh?

> Take a look at the ports tree as it stands. You'll notice that most
> ports don't include version numbers in their directory names. This makes
> upgrades easier when the time comes. Are you going to want a repository
> copy every time the minor version number bumps?

Do you expect RH to have minor version number bumps in their releases?
Do you think I need to follow every minor version number bump?

I don't think so.

> 
> > 2) I hope to import a linux-base-6.0 in the near future
> 
> This assumes that the first reason you gave was a good one, though.

Well, I thought so :-)

> Perhaps you should have linux-base and linux-base-devel?

Why linux-base-devel? what's wrong with linux-devel-[-version]???

> Have you read the porting section of the handbook?

Yes, and have paid special attention to the section about Package Names.
The language is 'linux'. The name is 'base'. No compiled specifics and the
version number is 5.2. Makes sense, don't you think. Where does it say in
the handbook that I should not use version numbers in directory names?

> > I think there's an advantage in having both *-5.2 and *-6.0 present in the
> > tree since I can't guarantee that Red Hat 6.0 supports all Linux binaries
> [...]
> 
> So these aren't Linux-compatibility ports, but rather
> RedHat-compatibility ports? Perhaps they should be named as such, then?

By your logic linux_lib was also not a Linux-compat port, but a
Slackware-compat port (IIRC that it was based on Slackware that is :-).

Come on... what's really the problem here? Why complain now when you had
every opportunity to complain when I posted my "why, how, when, what, etc,
etc..." in freebsd-emulation?

-- 
Marcel Moolenaar                                  mailto:marcel@scc.nl
SCC Internetworking & Databases                     http://www.scc.nl/
Amsterdam, The Netherlands                         tel: +31 20 4200655


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3784A0E8.C0394E82>