At 18:31 Uhr -0500 18.01.2002, Kyle Moffett wrote: > On Friday, January 18, 2002, at 06:04 , Max Horn wrote:
[...] >Sorry, this was just a kind of thinking out loud email, improving as >I went along, and really, whatever format we choose ought to be >reviewed here before anything solid is decided. Sure thing, same for my examples, I just wondered if there was a particular reason for that line. No problem :) [...] At 18:44 Uhr -0500 18.01.2002, Kyle Moffett wrote: >Just had another idea, for stuff like emacs-alpha, add an alpha >variant, with a different version number, and make it non-default ><version name="alpha" default="false">, so: I don't particulary like that idea, now. variants/options should be just that. In the case of emacs-alpha, we are really talking a radically different beast, with a Carbon base front end, and a different version number. >if default is true, ask user if they want to install dependencies. >if default is undef, install if all dependencies are already installed. >if default is false, only ask user if '-ask' is specified on the command line. Something like this... need to think about it. >Also, for different variants, instead of trying to piece together >some scripts and stuff ourselves, we could use diff, and have the >main version directly under <package> and then ><variant name="ssl"> > <compilescript type="diff"/> ></variant> ><variant name="alpha"> > <compilescript type="replace"/> ></variant> Hm, I think in most cases, diff would be quite some overkill. I think the following should always be sufficient if the package is cleanly designed: "prepend", "append", "replace" ? The default would be "append" as it is currently. In additon, a "diff" would be quite tricky, since the data it would be applied to would be different depending on which combination of variants is used, which essentially makes this not feasible, I think. Which leads to another thing: order in which variants are applied. For scripts this can be important. So we should allow a way to change the order. Of course, if a variant depends on another, that already induces some sort of order, but we do not always have a dependency and still need the ordering... hm. Next point: version specificatios. We can either use the dpkg format, like in "<<2.0" etc., or we use something custom, like I briefly mentioned in my previous post. Both have merits... <sigh>, so many choices =) Max -- ----------------------------------------------- Max Horn Software Developer email: <mailto:[EMAIL PROTECTED]> phone: (+49) 6151-494890 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
