Mailinglist Archive: zypp-devel (59 mails)
| < Previous | Next > |
Re: [zypp-devel] Catching file conflicts
- From: Federico Lucifredi <flucifredi@xxxxxxxxxx>
- Date: Tue, 18 Nov 2008 14:10:00 -0500
- Message-id: <49231308.6040005@xxxxxxxxxx>
Klaus Kaempf wrote:
Yah, looks like a lot of overhead.
They are not in our own packages :-) Third parties... the horrors there should not be discounted.
Probably the solution is that if someday we move away from force-nodeps towards transactions, file conflicts would be then caught at runtime by rpm.
Best -F
--
_________________________________________
-- "'Problem' is a bleak word for challenge" - Richard Fish
(Federico L. Lucifredi) - flucifredi@xxxxxxxxxx
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
* Federico Lucifredi <flucifredi@xxxxxxxxxx> [Nov 17. 2008 19:44]:
Would it be possible to examine the package before installation, to check for the files it contains against the RPM db or the filesystem ?
Technically, yes. But it would required parsing the RPM header of
every downloaded package, iterating through its filelist and searching
each entry in the rpmdb. And this would not catch conflicts againts
packages of the same transaction.
Yah, looks like a lot of overhead.
Its probably not worth the effort. Arbitrary file conflicts are very,
very seldomly needed.
They are not in our own packages :-) Third parties... the horrors there should not be discounted.
Probably the solution is that if someday we move away from force-nodeps towards transactions, file conflicts would be then caught at runtime by rpm.
Best -F
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
_________________________________________
-- "'Problem' is a bleak word for challenge" - Richard Fish
(Federico L. Lucifredi) - flucifredi@xxxxxxxxxx
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |