Hi folks,
I was wondering: Is there any sane way to specify a "common" splitoff
for a package with variants? The background for this questions it the
polymake package on our package submission tracker <https://
sourceforge.net/tracker/?
func=detail&atid=414256&aid=1114201&group_id=17203>, but I am now
wondering about this in general...
To explain what I mean, here an example: Assume you are making a
package FOO, which contains a few perl .xs files, so you need to use
Type: perl (...). But most files in the package (many many files,
which maybe take hours to compiler) are identical across all perl
versions, so it seems kind of a waste to keep two builds of them
around. So you would like to keep those files in a shared package.
What would you guys think is the best way to tackle this? Is it even
possible / sensible? Some ideas I had:
* Ignore that some stuff is common and simply have FOO-pmXXX w/o any
splitoffs -- after all, most users will build & install the package
once only anyway. So no need to worry about the common stuff.
* Make a FOO-common package with "FOO-pmXXX" splitoffs depending on
it. Problem: This enforces the dependencies of *all* variants to be
fulfilled (at least that's what trial&error tells me). In particular,
one has to install perl581-core to be able to build FOO-pm586 (at
least for me using Fink CVS from yesterday).
In addition to all this, the fact that there are some perl modules
used is in the end irrelevant for the users. They want FOO. They
don't care if it's perl 5.8.1 or 5.8.6. Hence, you want them to be
able to type "fink install FOO" and it does the right thing (the user
still has to pick which perl version to use, but that's OK). You
don't want your users to figure out that they have to install "FOO-
pm586" instead of "FOO".
This latter issue could probably be solved by using a separate "FOO"
bundle package I guess. Is that the way to go, I wonder? I also toyed
with making this bundle/wrapper package a splitoff, but then you
quickly run into problems again (or at least I did), like being
forced to build perl581-core and stuff like that.
Argh. I guess I am just missing something obvious or thinking way to
complicated. Guess I shouldn't mess with this stuff that late at
night ;-).
Cheers,
Max
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
