On 02/01/2012 04:41 PM, Chris Adams wrote:
Once upon a time, Emanuel Rietveld<codehotter@xxxxxxxxx> said:
On 02/01/2012 01:32 PM, Panu Matilainen wrote:
To-be-installed files obviously have no on-disk fingerprints, so it
wont work for initial installation. So yes, those "fake" compatibility
provides are needed. Strictly speaking, compatibility provides would
be needed for ALL the moved files, not just /bin, as it's technically
perfectly legal for a package to depend on an arbitrary path in
/lib[64], not just /[s]bin.
- Panu -
Would it be possible to leave out these provides and fix each individual
package to require in the new path instead?
It isn't practical to "fix" every package that requires /bin/sh.
It's not "just" that the impracticality either - not providing /bin/sh,
/sbin/ldconfig and the like would mean a huge incompatibility break with
nearly every existing package in the wild. Not really an option.
- Panu -
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
