[Slackbuilds-users] Needing requirements built with options

[Ryan P.C. McQuen]

If that is what everyone else thinks is reasonable that is fine with me.


---
<ryanpcmcquen.com>


> On Jul 14, 2014, at 3:52 PM, Doogster <thedoogster at gmail.com> wrote:
> 
> I would prefer that the only hard dependencies specified for gst1-plugins-bad be the ones that gst1-plugins-bad need in order to be built.
> 
> If you start specifying optional dependencies as hard ones because unrelated packages need them, then you end up with a mess like Debian where installing Mutt on your headless server installs X.
> 
>> On Monday, July 14, 2014, Ryan P.C. McQuen <ryanpcmcquen at gmail.com> wrote:
>> 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?
>> 
>> 
>> ---
>> <ryanpcmcquen.com>
>> 
>> 
>> > 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/
>> >
>> _______________________________________________
>> 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/
> _______________________________________________
> 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/
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20140714/7a91945f/attachment.html>