public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new package
Date: Thu Feb 22 10:29:02 2001	[thread overview]
Message-ID: <20010222102852.A22862@cvs.gentoo.org> (raw)
In-Reply-To: <3A954239.555AAE3A@gottinger.de>; from AGottinger@t-online.de on Thu, Feb 22, 2001 at 05:45:45PM +0100

On Thu, Feb 22, 2001 at 05:45:45PM +0100, Achim Gottinger wrote:

> The only package that really needs care is ORBit. About 50 packages are in
> dev-perl.  I personaly thought that using the sources name as we did it till
> now makes more sense since it reduces the typing in the scripts.  But if you
> guys are not happy with that change it.

Yes, the reason why we have uppercase is because the original archive name /
source directory also has uppercase.  This means that all the defaults get set
up correctly.  For this reason alone, I think we should allow uppercase
characters in /usr/portage.

Exceptions:
	If we are using uppercase for a package name, and the corresponding archive
	or source directory doesn't use uppercase characters, then this should be 
	fixed so that we're using lowercase.

This helps me to understand why MacOS X added case insensitive file comparison
routines.  Ideally, I'd like the filesystem to preserve the original case but
have:

# cat foo

and

# cat Foo

and

# cat fOo

...cat the same file.

After all, "D" and "d" are both a "d".  I'll see if I can track down a really
interesting message about this that I can forward to the list.

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			



  reply	other threads:[~2001-02-22 17:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-20 16:19 [gentoo-dev] new package Pete Gavin
2001-02-20 16:23 ` Jerry A!
2001-02-20 16:35   ` Pete Gavin
2001-02-20 17:43   ` drobbins
2001-02-22  9:22   ` Pete Gavin
2001-02-22  9:29   ` Achim Gottinger
2001-02-22  9:37   ` Achim Gottinger
2001-02-22  9:58     ` Jerry A!
2001-02-22 10:12       ` Achim Gottinger
2001-02-22 10:29         ` drobbins [this message]
2001-02-22 10:36           ` Achim Gottinger
2001-02-22 11:05             ` Jerry A!
2001-02-22 11:07               ` drobbins
2001-02-22 11:37                 ` Jerry A!
2001-02-22 12:10                   ` Achim Gottinger
2001-02-22 12:12                     ` drobbins
2001-02-22 12:27                       ` Achim Gottinger
2001-02-22 12:48                         ` Jerry A!
2001-02-22 11:24               ` Achim Gottinger
2001-02-22 10:37         ` Jerry A!
2001-02-22 10:42           ` Achim Gottinger
2001-02-22 11:02             ` Jerry A!
2001-02-22 11:46               ` Achim Gottinger
  -- strict thread matches above, loose matches on Subject: below --
2001-03-11 14:54 Pete Gavin
2001-03-11 15:51 ` drobbins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010222102852.A22862@cvs.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox