Re: Bug#40706: Reasons for not moving at all
Jason Gunthorpe wrote:
>
>
>On 21 Jul 1999, Philip Hands wrote:
>
>> Gordon Matzigkeit <gord@fig.org> writes:
>>
>> > Can somebody remind me again why it's so important to be FHS-compliant
>> > on this issue? Why not just change the few /usr/share/doc packages
>> > back to /usr/doc,
>>
>> Because people who want to save disk space by mounting architecture
>> independant directories from a common NFS server, say, really need to
>> have all the architecture independant bits under one subdirectory.
>
If /usr/share is NFS-mounted (which is the whole point, isn't it?), what
is to be done about packages being installed on networked machines, when
those packages want to update /usr/share/*/...? If different releases are
installed on different machines, there will be clashes between machines,
and there is no mechanism to resolve them. dpkg is not, as far as I know,
even aware that there is a problem. As things stand, there is no
guarantee that the files in /usr/share/* are actually the files that
belong to the package installed on your machine; they could belong to a
substantially different release installed on another machine.
Am I missing something here?
It seems to me that a policy and a mechanism are needed for managing files
that are installed in shared directories
--
Vote against SPAM: http://www.politik-digital.de/spam/
========================================
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
========================================
"Finally, all of you, live in harmony with one another;
be sympathetic, love as brothers, be compassionate and
humble. Do not repay evil for evil or insult for
insult, but with blessing, because to this you were
called so that you may inherit a blessing."
I Peter 3:8,9
Reply to: