On 26 July 2012 19:32, Michał Górny <[email protected]> wrote:
> But you are aware that this is *upstream* naming?
>
> Similarly, ati-drivers (which is not upstream naming :P)
> and nvidia-drivers don't follow the suite.
I wasn't aware of that, but thats beside the point I was trying to
make. Its just a mechanism that allows an appoximation of a 3-tier
system without needing a 3-teir system.
ie: sys-firmware/video/ati approximated as sys-firmware/video-ati ,
which seems slighly better than the competing ways of doing it like:
firmware-video/ati-firmware
firmware-video/ati
and any category name with "Firmware" in it, will result in lots of
redundant names exposed to users/deps if the package /also/ has
firmware in the name.
There's also the other thing to consider, and thats there's a lot of
hardware related stuff that is similar to firmware in a way, but also
totally devoid of a central category for it. Namely, kernel level
drivers. ( Which are not /that/ far removed from firmware, considering
that you can compile firmware into kernels and they're of similar
levels of necessity ).
We may as well suggest sys-hardware/ and put things like tp_smapi
and prism54-firmware all in that one category.
In essence, the rationale behind having a sys-firmware category for
all firmware, but no sys-drivers category for all device
drivers/modules seems an oversight.
But I think however you do it, the absence of a 3-tier system hamstrings you.
net-wireless/prism54-firmware ->
Alternatives:
sys-firmware/prism54-firmware
sys-firmware/prism54
sys-firmware/wireless-prism54-firmware
sys-firmware/wireless-prism54
firmware-wireless/prism54-firmware
firmware-wireless/prism54
sys-hardware/prism54-firmware
sys-hardware/wireless-prism54-firmware
hardware-wireless/prism54-firmware
net-dialup/hsfmodem ->
Alternatives:
sys-driver/hsfmodem
sys-driver/dialup-hsfmodem
sys-hardware/hsfmodem
sys-hardware/dialup-hsfmodem
hardware-dialup/hfsmodem
The perk of *not* having 'firmware' in the category name means you can
put drivers in the category as-is, and add firmware to the category
as-is, without needing to have redundant information. In a
sys-hardware/* hardware-$class/* layout, things without "-firmware"
are assumed kernel drivers , and things with -firmware are known as
firmware.
--
Kent
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"
