On Mon, Dec 08, 2003 at 08:11:51AM -0500, David R. Morrison wrote:
> Dan,
>
> When I expanded "Type: perl" to allow "Type: perl 5.x.y" back in June,
> I stuck the version number into the same field because I was getting
> flack about unnecessarily increasing the number of fields. However,
> in w
Dan,
When I expanded "Type: perl" to allow "Type: perl 5.x.y" back in June,
I stuck the version number into the same field because I was getting
flack about unnecessarily increasing the number of fields. However,
in wedging it in there I did some less-than-pretty things to the code!
One thing w
Okay, I'm now parsing the Type field for the version of perl. The code
is extensible to other versionable languages (python, etc.). A bit of
syntax change to Type: would probably a allow upgrading to handle
multiple language keys (or other variants) in a logical AND meaning by
putting them all in a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Max Horn wrote:
| 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
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'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthias Neeracher wrote:
|> From: Daniel Macks <[EMAIL PROTECTED]>
|>
|> We've got a lot of packages that are the same module for different
|> versions of a language (-pm*, -py*, etc.). Often, the only difference
|> between these .info files is in the
From: Daniel Macks <[EMAIL PROTECTED]>
We've got a lot of packages that are the same module for different
versions of a language (-pm*, -py*, etc.). Often, the only difference
between these .info files is in the %n and some Depends and pathnames
in *Scripts, and these are either the language versi
We've got a lot of packages that are the same module for different
versions of a language (-pm*, -py*, etc.). Often, the only difference
between these .info files is in the %n and some Depends and pathnames
in *Scripts, and these are either the language version or a condensed
form of it. What do pe
