Re: [Fink-devel] Re: How to test the two variants of a package?

2004-04-08 Thread Alexander Strange
On Apr 8, 2004, at 4:57 PM, Daniel E. Macks wrote: Package: gimp%type_pkg[-noprint] Type: -noprint (boolean) Conflicts: gimp, gimp-noprint Replaces: gimp, gimp-noprint This will definitely be a lot of typing, since each of those also has the -svg variant. An easier way would be nice, but I

[Fink-devel] Re: How to test the two variants of a package?

2004-04-08 Thread Daniel E. Macks
(I think this didn't go to the list...trying again, and with corrections to example at the end) Martin Costabel <[EMAIL PROTECTED]> said: > Daniel Macks wrote: > [] >> You're getting yourself *way* too worked up about variants, Martin. > > I get worked up about anything that doesn't work correctl

[Fink-devel] Re: How to test the two variants of a package?

2004-04-08 Thread Daniel E. Macks
Martin Costabel <[EMAIL PROTECTED]> said: > > BTW, fink validate doesn't yet seem to understand variants completely: > > % fink validate bluefish.info > Error: Package name may only contain lowercase letters, numbers,'.', '+' > and '-' (bluefish.info) Fixed (I think) in CVS HEAD. dan -- Dani

Re: [Fink-devel] Re: How to test the two variants of a package?

2004-04-08 Thread Martin Costabel
Daniel E. Macks wrote: I just implemented 'fink dumpinfo [pkgname]' in CVS HEAD so you can see how fink parses a package description, including percent expansion (and hence variant info), and conditional Depends. This is certainly useful, especially since it allows to extract splitoffs, even for

[Fink-devel] Re: How to test the two variants of a package?

2004-04-07 Thread Daniel E. Macks
Daniel E. Macks <[EMAIL PROTECTED]> said: > David R. Morrison <[EMAIL PROTECTED]> said: >> Just to clarify: my understand of Michele's problem is that when she tries >> to build the two variants contained in this .info file, only one of them >> can be built. >> >> So either it's a problem with th

Re: [Fink-devel] Re: How to test the two variants of a package?

2004-04-07 Thread Daniel Macks
On Thu, Apr 08, 2004 at 02:48:37AM +0200, Martin Costabel wrote: > Daniel E. Macks wrote: > > > >Variants make it easier for the Maintainer to maintain multiple > >variants (in the conceptual, not Fink sense) of a package. It relieves > >what was becoming (became?) an unscalable mess of -pmXXX (a

Re: [Fink-devel] Re: How to test the two variants of a package?

2004-04-07 Thread Michèle Garoche
Le 8 avr. 2004, à 2:05, Daniel E. Macks a écrit : David R. Morrison <[EMAIL PROTECTED]> said: Just to clarify: my understand of Michele's problem is that when she tries to build the two variants contained in this .info file, only one of them can be built. So either it's a problem with the way

Re: [Fink-devel] Re: How to test the two variants of a package?

2004-04-07 Thread Martin Costabel
Daniel E. Macks wrote: Variants make it easier for the Maintainer to maintain multiple variants (in the conceptual, not Fink sense) of a package. It relieves what was becoming (became?) an unscalable mess of -pmXXX (and -pyXXX and -rbXXX, etc.) packages. Do you really believe that all those modul

[Fink-devel] Re: How to test the two variants of a package?

2004-04-07 Thread Daniel E. Macks
David R. Morrison <[EMAIL PROTECTED]> said: > Just to clarify: my understand of Michele's problem is that when she tries > to build the two variants contained in this .info file, only one of them > can be built. > > So either it's a problem with the way she has constructed the file, or > a proble

[Fink-devel] Re: How to test the two variants of a package?

2004-04-07 Thread Daniel E. Macks
Martin Costabel <[EMAIL PROTECTED]> said: > > But I don't think one should produce packages that one cannot test. Absolutely. But... > That's why I don't like this whole variant thing. That seems kind of orthogonal. Variants make it easier for the Maintainer to maintain multiple variants (in th