On Thu, Feb 23, 2012 at 2:03 AM, David C. Rankin
<drankinatty@...> wrote:
> On 02/22/2012 05:21 PM, Pawel Soltys wrote:
>> On Wed, Feb 22, 2012 at 9:23 PM, David C. Rankin
>> <drankinatty@...> wrote:
>>> Calvin, Baho, Pawel,
>>>
>>>  Why do we need 'libutempter'? I've never heard of it before. I don't mind
>>> having an AUR package, but if we ever hope to have TDE picked up by Arch, it
>>> needs to build on Arch. Do we really need libutempter?
>>>
>> I decided on including support for utempter because someone might need
>> it. The PKGBUILDs by default build trinity with support for
>> everything. Customize if you don't want it. That's why the pkgbuilds
>> (and abs) exist in the first place. ;)
>>
>
> What about adding 'libogg' as a dependency for tdelibs or arts (I don't know
> exactly where it is best in the build), but I would like to see ogg support
> built in. Will tdelibs use it if it is already installed - or does it matter?
>
libvorbis which is dependency of arts provides ogg/vorbis support.
Having libogg as a direc dependency is not needed, since libogg is
libvorbis dependency and thus becomes an indirect dependency. Even if
you don't include it as dependency of arts, it still will be installed
(as libvorbis dep) and used.
If you were to include it and examine package with namcap you'll see
that namcap gives you message like "libogg included but already
satisfied".
Keep the dependencies minimal. Include only direct dependencies in pkgbuilds.