Trevor Harmon wrote:
Why not make saxon81 and saxon82, and have them both Provide: saxon
Ah, I forgot about Provides. However, I don't see a reason to make
separate packages for saxon82, saxon83, saxon84, etc. I think I'll just
do a saxon811 and a saxon8, both of which will provide saxon. Th
On Dec 7, 2005, at 8:54 PM, Benjamin Reed wrote:
Why not make saxon81 and saxon82, and have them both Provide: saxon
Ah, I forgot about Provides. However, I don't see a reason to make
separate packages for saxon82, saxon83, saxon84, etc. I think I'll
just do a saxon811 and a saxon8, both o
Trevor Harmon wrote:
One way of solving this is to provide two packages, saxon and saxon811.
Each package can reference the other in its Conflicts field. However,
this means that packages depending on *any* version of Saxon must
specify "Depends: saxon | saxon811". Otherwise (if they only spec