King Beowulf skrev 2014-07-14 03:09:
Thanks for the heads-up. I need CUDA/OpenCL support right now. Using the
.run-file will give me the nvidia-uvm device.
Regards,
Mats
You just need to run OPTAPPS=yes ./nvidia-driver.SlackBuild to compile
it. After reboot, run as root nvidia-modprobe -c 0
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
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
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
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
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 thedoogs...@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
On 7/14/14, Doogster thedoogs...@gmail.com wrote:
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?
That's something
IMO, you should also list libmodplug as a dep in inform7's info file. List
it first (or at least, before gst-plugins-bad). If people are installing
the deps in the order listed in REQUIRES, it'll take care of itself
(because gst-plugins-bad will auto-detect that libmodplug is installed,
I'm also leaning towards the README thing. If a tool works by building and
then traversing a dependency tree data structure, then listing libmodplug
first will not guarantee that it's built first.
On Monday, July 14, 2014, David Spencer baildon.resea...@googlemail.com
wrote:
IMO, you should
