[Slackbuilds-users] Needing requirements built with options

Ryan P.C. McQuen ryanpcmcquen at gmail.com
Mon Jul 14 21:45:13 UTC 2014

If there are other situations meriting gst1-plugins-bad built against libmodplug, wouldn't it be worth it to make it a hard dependency? Does anyone really mind one extra package if it means better compatibility down the road?


> On Jul 14, 2014, at 2:39 PM, King Beowulf <kingbeowulf at gmail.com> wrote:
>> On 07/14/2014 02:08 PM, Doogster wrote:
>> I'm about to submit a new version of gnome-inform7, and I've run into a
>> problem. It requires gst1-plugins-bad, and it needs gst1-plugins-bad to
>> have been built with libmodplug support. The problem is that
>> gst1-plugins-bad lists libmodplug as an optional dependency, not as a
>> hard one. How should I handle that,
>> The best solution I can think of is to specify gst1-plugins-bad in the
>> info file as a hard requirement, then mention in the README that
>> gst1-plugins-bad needs to have been built against libmodplug. Is there a
>> better way?
> IMO,  think that is the best way.  Specify the dep in .info, then give
> "gotchas" in the README.  This might trip up the sbopkg users, but short
> of including a "special" gst1-plugings-bad, it'll be hard to cover every
> use case.  After all, we should all be reading the README, right?
> -Ed
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/

More information about the SlackBuilds-users mailing list