[Fink-devel] versioning Depends in info files
Is there a way to get the dependency engine to accept a specific version of another package but wildcard the revision field when searching? For example, I want Package A to depend on Package B-0.3.3, but I don't care what revision of Package B (eg 0.3.3-1 and 0.3.3-7 are OK, but 0.3.4-1 is no longer ok). I tried setting Depends to (= %v), but this gives me an error that Package B (= 0.3.3) has no matching package/versions found. Right now I'm using Depends: Package B (= %v), but this will invariably be affected once the package version gets increased. In other words, I don't want to hard code the revision number in case the Depended package changes in such a way that doesn't affect the functionality. Hanspeter -- The great tragedy of science is the slaying of a beautiful hypothesis by an ugly fact. --Thomas Henry Huxley --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] versioning Depends in info files
On Aug 23, 2004, at 10:33 AM, Hanspeter Niederstrasser wrote: Is there a way to get the dependency engine to accept a specific version of another package but wildcard the revision field when searching? Hi Hanspeter, For my Galeon package I have to depend on a specific major version of Mozilla, eg: 1.7.*-* . The way I do this is: Depends: mozilla (= 1.7-1), mozilla ( 1.8-1) There are certain cases where this wouldn't work I guess, for example if Mozilla decided that instead of 1.8a1 they'd call it 1.7.99. But usually it works, and you can do the same sort of thing for your package. Dave PGP.sig Description: This is a digitally signed message part
Re: [Fink-devel] versioning Depends in info files
Dave Vasilevsky wrote: On Aug 23, 2004, at 10:33 AM, Hanspeter Niederstrasser wrote: Is there a way to get the dependency engine to accept a specific version of another package but wildcard the revision field when searching? Hi Hanspeter, For my Galeon package I have to depend on a specific major version of Mozilla, eg: 1.7.*-* . The way I do this is: Depends: mozilla (= 1.7-1), mozilla ( 1.8-1) Did you actually try this? And did it do what you thought it should do? In my tests, when it was like you show it, it happily neglected the second dependency and installed the higher version anyway. When I interchanged the the two inequalities, put the first and the = second, I got the infamous node ... already exists error. -- Martin --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] versioning Depends in info files
On Aug 23, 2004, at 5:21 PM, Martin Costabel wrote: Depends: mozilla (= 1.7-1), mozilla ( 1.8-1) Did you actually try this? And did it do what you thought it should do? In my tests, when it was like you show it, it happily neglected the second dependency and installed the higher version anyway. When I interchanged the the two inequalities, put the first and the = second, I got the infamous node ... already exists error. Er, I didn't test it, but I think dpkg should deal with it fine, and apt-get too. I guess Fink's dep engine can't. The other alternatives are: 1) Make A depend on a specific revision of B, and then keep in touch with B's maintainer and/or subscribe to fink-commits. 2) Make a separate package Bxxx for just the required version, like we had with db317 for a while. Dave PGP.sig Description: This is a digitally signed message part
