On Mon, 11 Jun 2012 23:16:09 +0200, Peter Dyballa <peter_dyba...@freenet.de> wrote:
> Am 11.06.2012 um 17:52 schrieb Alexander Hansen: > > >> Files: lib/lib*.*.dylib > >> Shlibs: << > >> %p/lib/libMagick++.5.dylib 6.0.0 %n (>= 6.7.7-6) > >> %p/lib/libMagickWand.5.dylib 6.0.0 %n (>= 6.7.7-6) > >> %p/lib/libMagickCore.5.dylib 6.0.0 %n (>= 6.7.7-6) > >> << > >> DocFiles: LICENSE README.txt ChangeLog NEWS.txt > >> << > >> >> Why can't I use %V as in (>= %V)? (Although I presume that the > version number does not play a role...) And similarly here: > >> > > You mean in the Shlibs field? You presume incorrectly. It's in the > > packaging manual. > > > The Shlibs declaration is to specify the _first_ version-revision of a > > package where a library with a given install_name appears with a given > > compability_version. > > > Thus, if upstream makes an updated version of the package but doesn't > > change the install_name or compatibility_version of the libraries, then > > your libraries should still be the same, and you keep the _same_ Shlibs > > fields in the new version of the package. > > So I can leave there some old version number, 6.5.7-1? > > > > The only way to create your own percent expansions is to use Type. For > > example: > > > Type: v (6.7.7) > > > This gives you the options: > > > %type_raw[v] = 6.7.7 > > %type_pkg[v] = 677 > > This is not satisfying, I still would have to update one more version > number manually, one more than used for the Version field. There is an intentional intent to make you have to think when you change things in the Shlibs field, because if you do it wrong you create something between a headache and a massive and diffcult-to-resolve breakage for dozens of other packages you don't control--exactly the things fink (as a project) aims to avoid by policy. Every different part and value has a specific meaning that all work together so that end users don't have to deal with these sorts of problems (trade-off is the small pain for maintainers). Please don't try to subvert a very simple declaration of "this is what the file is, this is when it first appeared" with a fragile hack. I suspect you've already spent more time trying to find one than just cut'n'pasting the value. dan -- Daniel Macks dma...@netspace.org ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
