Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-28 Thread Pixel
"Hoyt" [EMAIL PROTECTED] writes: So if you were to create a shell script to do this named, for example, "whatrpmprovides", what would it look like? (I'm a writer, not a programmer). there is urpmi that takes care of dependencies. have a look at /var/lib/urpmi/depslist also look at urpmf

Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-26 Thread Guillaume Cottenceau
"Hoyt" [EMAIL PROTECTED] writes: Nothing is more annoying than to try and intall an rpm and have it fail because of a dependency issue, only to 1)have =that= rpm fial because of another dependency issue, or 2) have the dependency be some library buried in an rpm that isn't easily

RE: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-26 Thread Geoffrey Lee
"Hoyt" [EMAIL PROTECTED] writes: Nothing is more annoying than to try and intall an rpm and have it fail because of a dependency issue, only to 1)have =that= rpm fial because of another dependency issue, or 2) have the dependency you are saying because package foo requires package

Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-26 Thread Denis HAVLIK
:~Nothing is more annoying than to try and intall an rpm and have it fail because of :a dependency issue, only to 1)have =that= rpm fial because of another dependency :issue, or 2) have the dependency be some library buried in an rpm that isn't easily :discernable. The program ezrpm address

Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-26 Thread Hoyt
- Original Message - From: "Geoffrey Lee" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 26, 2000 9:12 AM Subject: RE: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better you are saying because package foo requires package bar so you must also

Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-26 Thread Hoyt
- Original Message - From: "Guillaume Cottenceau" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 26, 2000 8:45 AM Subject: Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better "Hoyt" [EMAIL PROTECTED] writes: Nothing is more

RE: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-26 Thread Geoffrey Lee
you are saying because package foo requires package bar so you must also download package bar to satisfy pacakge foo right ?? just use rpm --force ...e.g. i don't insall the mandrake_desk package becuse i don't ened it so i use --force for wmaker. it's only in some cases that

Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-26 Thread Stephane Gourichon
On Fri, 26 May 2000, Hoyt wrote: just use rpm --force ...e.g. i don't insall the mandrake_desk package becuse i don't ened it so i use --force for wmaker. it's only in some cases that you should use --force anyway. --nodeps is less ... forcing. I often do just that =if= I understand

Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-26 Thread Hoyt
- Original Message - From: "Geoffrey Lee" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 26, 2000 12:02 PM Subject: RE: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better though i must admit that it's a litle hard to understand the

Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-26 Thread Hoyt
- Original Message - From: "Stephane Gourichon" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 26, 2000 11:55 AM Subject: Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better On Fri, 26 May 2000, Hoyt wrote: But that's a job to extend the rp

Re: [Cooker] GET READY FOR A DISCUSSION - Address dependency issue better

2000-05-25 Thread Hoyt
Nothing is more annoying than to try and intall an rpm and have it fail because of a dependency issue, only to 1)have =that= rpm fial because of another dependency issue, or 2) have the dependency be some library buried in an rpm that isn't easily discernable. The program ezrpm address some of