Jason Tackaberry wrote:
> On Fri, 2006-12-01 at 11:59 +0100, Dirk Meyer wrote:
>> Not each. Each module needs kaa.base, kaa.beacon needs
>> kaa.metadata. But others like kaa.xine and kaa.imlib2 don't have a
>> dependency to eachother.
>
> kaa.xine has a "soft" dependency on kaa.display -- that is,
On Fri, 2006-12-01 at 11:59 +0100, Dirk Meyer wrote:
> Not each. Each module needs kaa.base, kaa.beacon needs
> kaa.metadata. But others like kaa.xine and kaa.imlib2 don't have a
> dependency to eachother.
kaa.xine has a "soft" dependency on kaa.display -- that is, it will work
without kaa.display
TC Wan wrote:
> I can build them separately, as you describe. It's just a matter of
> figuring out the individual module dependencies and putting them in
> different SPEC files. Wish there was an easy way to create a meta-spec
> file for the different modules though.
Each module has a gentoo ebuil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Evan,
Which distro are you packaging for?
I can build them separately, as you describe. It's just a matter of
figuring out the individual module dependencies and putting them in
different SPEC files. Wish there was an easy way to create a meta-spe