[gentoo-dev] Re: RFC: split up media-sound/ category

[Paul Arthur]

On 2011-06-27, Jesús J Guerrero Botella
<jesus.guerrero.botella@×××××.com> wrote:

> 2011/6/27 Wyatt Epp <wyatt.epp@×××××.com>:
>
>> 2011/6/27 Jesús J. Guerrero Botella
>> <jesus.guerrero.botella@×××××.com>:
>>
>>> That still doesn't answer my question anyway: both features
>>> (symlinks and +65k files on a single dir) are incompatible with
>>> fat32. And someone said fat32 compatibility is a feature we want
>>> (still can't guess why, but well, be consequent...). Obviously,
>>> we want fat32 compatibility when it comes to arguing against
>>> symlinks, which have always been with us by the way, but that's
>>> not important when we talk about other things that are not
>>> compatible with fat32.
>>
>> I'm not sure where you're getting 65k files.  Unless I
>> misinterpreted everything everyone else was saying, every package
>> would still have its own directory.  There are fewer than 20k
>> even with a bunch of overlays installed.  Regardless, you might
>> check the other (other) thread; I think we're probably going to go
>> quick and not-necessarily-dirty with sets to get 99% of what we're
>> looking for almost trivially.
>
> Well, someone suggested a flat directory, which I understand as
> having all the ebuilds in a single directory, that's also why they
> are talking about the need to make ebuild names unique, to avoid
> file names collision.

Packages, not ebuilds. Getting rid of categories puts all of the
packages in the same directory, so you need unique package names.
So you might make app-arch/par parchive, dev-util/par palm-par, and
app-text/par par. par-1.52.ebuild would still live in $PORTDIR/par/

-- 
Please do not ask the Staff to use red text to ask Users not to hypothetically
appeal hypothetical future bans.
    --Cessna on RPGNet