[packman] Collective bugreport

Manfred Tremmel manfred at links2linux.de
Mon Mar 5 19:41:37 CET 2007


Am Montag, 5. März 2007 00:43 schrieb Jan Engelhardt:

> (6)
> Some packages have a lot of excessive Requires: tags, e.g.

Yes, and it is usefull! There are a lot of people not using tools (like 
apt or yast) to solve dependencies.

> ingen-0.4pre-0.pm.svn20070224. Picking a Require: from ingen,
>
> 	Requires: libxml2 >= 2.6
>
> This dependency is automatically added through the AutoReqProv
> mechanism (enabled by default) if there is a binary that links
> against libxml2.

No, it's not. A entry to libxml2.so.2 is added, not libxml2. Ok in this 
case, it's not so complicate to abstract the depending package, but 
others are more complex. And what's the result? Mails to the packager.

> (7)
> Just a hint: Quite every specfile uses %{macro}. However, RPM also
> accepts %macro, just as bash takes both $var and ${var}.

And like in shell scripts the version with {} is more save. %{macro}test 
works, but %macrotest can make problems.


> (8)
> Some specfiles have Packager:/Vendor:/etc. tags. These _do not_
> belong into specfiles, but your .rpmmacros file, or whatever is
> appropriate for the build system you are using. The full list is at
> the end of the mail. Examples:
> 	Lin3gp.spec:Vendor:         Packman
> 	MPlayer.spec:Vendor:            %vendor
> (Plus, Vendor: always defaults to %vendor so that line is redundant,
> but see (4).)

Sorry, I do not understand, what's the problem here.

-- 
Machs gut    | http://www.iivs.de/schwinde/buerger/tremmel/

Manfred      | http://packman.links2linux.de/





More information about the Packman mailing list