Date: Thu, 27 Jan 2005 14:04:21 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Oliver Lehmann <oliver@FreeBSD.org> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: cvs commit: ports/x11 Makefile ports/x11/Terminal Makefile distinfo pkg-descr pkg-plist Message-ID: <20050127220421.GA85114@xor.obsecurity.org> In-Reply-To: <20050127205120.49af3a0b.oliver@FreeBSD.org> References: <200501271827.j0RIRfeP052265@repoman.freebsd.org> <Pine.LNX.4.44.0501271232580.30725-100000@pancho> <20050127202704.1241613c.oliver@FreeBSD.org> <20050127193105.GA22233@xor.obsecurity.org> <20050127205120.49af3a0b.oliver@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--yrj/dFKFPuw6o+aM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jan 27, 2005 at 08:51:20PM +0100, Oliver Lehmann wrote:
> Kris Kennaway wrote:
>=20
> > On Thu, Jan 27, 2005 at 08:27:04PM +0100, Oliver Lehmann wrote:
> > >
> > > Even if the author of that software have choseen to write and use it
> > > uppercase?
> >=20
> > This is discussed in the porters' handbook.
>=20
> a)
> Yes it is.
> >>>>
> The first letter of name part should be lowercase. (The rest of the
> name can contain capital letters, so use your own discretion when you
> are converting a software name that has some capital letters in it.)
> <<<
> I don't see a "must" in that part.=20
>=20
> b)
> I think that "terminal" would be a much more collective term then
> "Terminal" is. Renaming it to xfce4-terminal is imho also a bad idea
> since thats just not its name and there might be a project called
> xfce4-terminal once - just because there is none right now.
>=20
> c)
> What makes "Terminal" different from "FreeBSD" when it comes to
> writing? We all want to see FreeBSD written as FreeBSD and not as
> freebsd. So why do we want to force other piece of software to
> be written in lowercase? Do we apply double standards?
>=20
>=20
> If you want me to back it out, I'll do so, but please reconsider...
The reason is that it's more difficult to locate the port when you
have to try to remember or guess the possible studlycaps, i.e. the
mapping is one to many.
e.g. if I'm looking for the port of security software called 'foobar',
I'll try to cd /usr/ports/security/foobar and not
/usr/ports/security/FoObaR. I actually run into this periodically,
and it's quite annoying to have to cancel the command, and visually
grep the directory listing to find the capitalized port directory.
The opposite case ("I want to know where in the ports collection is
the port of security software which I happen to know the authors
capitalize as FoObaR") is trivial to guess, if the port name is
correctly lower-cased, because the mapping is many-to-one.
It's not quite this simple because the rule isn't "port name should be
completely lower case", but the capitalization is usually on word
boundaries, so you can get there with shell filename completion.
Kris
--yrj/dFKFPuw6o+aM
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
iD8DBQFB+WVlWry0BWjoQKURAmTUAKCYW2eBnIcX2BIUGVdhGyzv7QtfWQCgwfM2
7uuz3eQmwi6efp+UW0UAoZo=
=+TZO
-----END PGP SIGNATURE-----
--yrj/dFKFPuw6o+aM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050127220421.GA85114>