Re: [OM Cooker] Odp.: Re: Odp.: Re: Makedev perl to bash conversion

Good intentions (rather than better QA) are unlikely to achieve success.

The problem is also worse than ordering installation of /etc/passwd before
the directory structure is installed so that uid/gid can be looked up.

On a bare metal installation (or an empty chroot creation), one also needs to
be able to lookup users/groups.

That basically means that ALL user/group lookups are NOT coming from
packaged content. 

Nor can that problem be meaningfully solved: one would have to restart
the install after glibc (with its lookup services) is installed to be able to
lookup the data in /etc/passwd.

But I digress ... It Really Doesn't Matter whether setup <-> filesystem
are combined or separate is all that I am saying.

The hardwired user/group lookups in RPM have been solving this chicken <-> egg
problem all century with nobody the wiser.

73 de Jeff

On Jul 30, 2013, at 12:37 PM, Per Øyvind Karlsen wrote:

> 2013/7/30 Jeffrey Johnson <[email protected]>
> 
> On Jul 30, 2013, at 12:23 PM, Per Øyvind Karlsen wrote:
> 
>> 2013/7/30 Tomasz Paweł Gajc <[email protected]>
>> It still provides dev and still owns /dev directory.
>> 
>> This has to be fixed and some parts need to be moved to filesystem and udev subpackage or kmod.
>> Speaking of, despite my objection previously, someone went ahead and merged the setup & filesystem package, which given that /etc/passwd needs to exist before the filesystem package in order for usernames to be available to set file ownership, just screws up further what was intended to be fixed.
>> 
>> Would be nice if this change would get reverted.
> 
> Reverting is perfectly sane if and only if setup is ordered before
> all other packages always.
> 
> Installing setup (for password lookup) isn't close to being true for any modern linux distro, and
> (last I looked) was particularly bad in  Mandriva based systems, with large numbers
> of dependency loop's.
> 
> Short answer:
> 	It simply does not matter whether you have combined setup+filesystem
> 	or separate setup and filesystem packages.
> Sure, it's an issue to address, and as we're currently left in this situation, it doesn't really matter (merging the two were a flawed attempt to resolve this), but I really hope to be able to address the ordering issue sometime in the not so distant future. :)
> 
> --
> Regards,
> Per Øyvind