Personally I feel this suggestion is far too narrow in scope. Why limit yourself to a "LangVersion" field if this can be used for other things? One thing that I worry about a lot is that people keep wanting to add very special purpose fields to fink. Sometimes you have to do that. But often it's better to first take a step back and look at the problem not just from your own personal perspective, but from a more more global one. Else we end up with dozens of special purpose fields which are only used in a handful packages each. Bad.

In this particular case, you seem to essential tackle the "Variants" problem we have discussed a lot in the past. Only that you are doing a limited special case of it. In particular, the naming suggest that it is only to be used for "Language variants". Furthermore, it can't cope with different dependencies etc. (except when those dependencies make use of the "LangVersion" data).

Of course sometimes it's simply much easier to first implement a special case (because e.g. the special case is simple and easy to code, while the full case is complex and hard to code). But at least try not to loose sight at the long run goal, and the broader scope of things. Else we design ourselves into a corner, IMO.


Max




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to