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. That
should work, right?
Yup.
The only thing I'm concerned about is packages that require a certain
version of saxon. For instance, "Depends: saxon (>= 8.4)" wouldn't work
because a Provides field can't have a version, correct? I guess in that
case the package will simply have to depend on saxon8 (>= 8.4). Not an
ideal solution, but I think it's the best in this case.
Exactly; that's how it should work. Welcome to the world of dependencies!
;)
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
