On Mon, Aug 17, 2009 at 09:12:16AM +0800, Zhang Sen wrote:
> Yes libgnome is already removed from gnome's build scripts, but it's in
> _our_ recipe. When I _cooked_ glade, it requires me to install libgnome
> things, but that's not actually needed.

you wrote that extra BuildRequires will lead to unneeded dependencies.
but if libgnome is not in the build script it will not be used, and it
will NOT lead to unneeded dependencies. if the resulting binary still
depends on libgnome, then the build scripts still cause it to be linked,
which means libgnome is not yet removed.

is this the case here? 
do the binaries still depend on libgnome?

does conary report libgnome as an unused BuildRequires?

> Anyway this is no big thing, if there is no wonderful solutions, oh
> well..

what kind of solution do you want?
should the build fail for unused BuildRequires? that would just cost
time. do you want an easier way to find the unused BuildRequires after
baking all of the gnome dev kit? since there are hundreds of packages
maybe you want a summary report? i guess this cold be done with a
script. (how is the dev kit built? with rmake or cvc? are all packages
built in a single rmake or cvc command?)

greetings, martin.
-- 
cooperative communication with sTeam      -     caudium, pike, roxen and unix
offering: programming, training and administration   -  anywhere in the world
--
pike programmer      working in china                   community.gotpike.org
foresight developer  foresightlinux.org                        open-steam.org
unix sysadmin        iaeste.(tuwien.ac|or).at                     caudium.org
Martin Bähr          http://www.iaeste.or.at/~mbaehr/            is.schon.org
_______________________________________________
Foresight-devel mailing list
Foresight-devel@lists.rpath.org
http://lists.rpath.org/mailman/listinfo/foresight-devel

Reply via email to