On Thu, Jan 15, 2004 at 12:51:44PM +0100, Max Horn wrote: > > Am 15.01.2004 um 12:34 schrieb Daniel Macks: > > >Matthias Neeracher <[EMAIL PROTECTED]> said: > > > >>--- NEW FILE: imlib2-rb18.info --- > >>Package: imlib2-rb18 > >>Depends: ruby18-shlibs, imlib2-shlibs > >>BuildDepends: ruby18-dev, imlib2 > >>Type: ruby 1.8 > >>InstallScript: << > >>make install prefix=%i > >>mkdir -p %i/share/doc/%n > >>cp -r examples doc %i/share/doc/%n > >><< > > > >Does this rely on any of the magic you just added to Fink::PkgVersion? > > It does, the "Type" value is new. Hence the package must build depend > on the first fink version to support this feature. Which in this case > is a not release version of fink...
As of fink-0.18.0, that's an allowed value. Validation.pm started allowing it on 22 December, and I think by 23 December at the latest the PkgVersion.pm parser of the Type field accepted other languages as well. But overall you're right, the more serious question is if this package relies on *anything* that would make this .info not work for recent fink releases. In this case, that would be a different default CompileScript I think. > strictly spoken this package > shouldn't even be in CVS at this point, but rather should've been > delayed till at least some version of fink with ruby support got > released.... But done is done, so at least add the BuildDepends field, > please. Or just hard-code the CompileScript? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
