On Thu, 14 Feb 2002, Alexander Skwar wrote:
> > > libxml-devel, libscrollkeeper-devel: libgnome32-devel
> > Are you sure about these?
>
> Scrollkeeper: Yes. XML: Might be.
maddog@mobile 21:25:35 ~> rpm -q libscrollkeeper0-devel
libscrollkeeper0-devel-0.2-1mdk
maddog@mobile 21:25:45 ~> rpm -ql libscrollkeeper0-devel
/usr/lib/libscrollkeeper.a
/usr/lib/libscrollkeeper.la
/usr/lib/libscrollkeeper.so
maddog@mobile 21:25:56 ~> grep dependency_libs /usr/lib/libscrollkeeper.la
dependency_libs=''
maddog@mobile 21:26:04 ~> ldd /usr/lib/libscrollkeeper.so
libc.so.6 => /lib/libc.so.6 (0x40026000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
Don't see anything vaguely related to X here. Same applies for
libxml-devel. Am I wrong?
> > > gettext-devel, bison, byacc, libbzip2-devel: rpm-build
> > I believe no or very few packages can build without rpm-build :)
>
> Well, it's not *strictly* necessary, however the reason why I'd include
> these in rpm-build is that many packages require the above packages.
> And I don't think it would be right to mention all of the above in each
> and every package. It's kinda like requiring gcc or glibc in every
> package, no?
Yes, that's what I mean. Adding rpm-build is kinda like adding gcc to,
say, 70% of all Mandrake packages.
> I'd like to have a setup where I only need to specify one package and
> get a whole set of needed development packages installed right away.
You have already made it clear. Agreed.
> Or would it be correct if I'd Require: *every* package that the new
> package needs? With this I mean, that I'd require glibc, bash,
> filesystem, rpm ....
Definitely not. These are requirement of basesystem, and the whole
system won't run well at all without these stuff.
I have some basic idea on how to determine the requirements of devel
packages:
1. parse foobar.la and foobar.pc, see if any libraries/.pc/.la files are
listed as requirement. These are non-versioned dependencies.
2. grep '^#.*include' /usr/include/foobar, see if any headers are
required by the specified devel package. These can be versioned or not,
depending on content of configure.in.
Stefan, any comment?
Abel
> Alexander Skwar
>