Alternative dependencies

[uggla]

Hi!

I have created an extension which requires Python >2.4. That means that a whole bunch of different Python extensions in the repo would work. Is it possible to add python*.tcz or something similar to the .dep-file?

regards
/Uggla

[tinypoodle]

Perhaps http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/tcz/edna.tcz.info could serve as an example of precedence of a possible approach to this subject.  

[Juanito]

I'd suggest to use the latest - python-2.7.tcz

[uggla]

Wouldn't it be a good idea if you could give alternatives on a line in the dep-file?
For example like this:
python.tcz|python-2.7.tcz|python-2.5.2

/Uggla

[tinypoodle]

No, dep files serve (non interactive) automatisation.

[uggla]

No, dep files serve (non interactive) automatisation.

Why couldn't it still be?

When loading an extension it could try to load each of the dependencies in the list and move on to the next line as soon as it succeeds.

When installing an extension the presence of any of the alternatives should be checked and if none is found then install the first one.

[andriscom]

I think this would be a good thing! 

[gerald_clark]

What if the next package requires the second dependency in that list, and the two are incompatible?

[Frank]

Then you are in exactly the same situation as now, where the list comprises only the first dependency.

[tinypoodle]

uggla,

have you - or has anyone else reading this - ever seen such a solution implemented?

[hiro]

Write it into the info file and let the user decide which package to install...

[uggla]

uggla,

have you - or has anyone else reading this - ever seen such a solution implemented?

Not really, but I think rpm can handle alternative dependencies.

[hiro]

I admit that I once also had been fighting against the feeling of needing this feature.
But thinking about how to implement it I also understood why it doesn't work on any other system either...