Andrew Brouwers wrote:
$ grep -i maintainer nvidia-driver.info
MAINTAINER="ppr:kut"
More appropriate than spamming the entire list.
Heh, and then you send that to the entire list, when Phillip's email
address was right there ;-)
Really, I don't see his email to the list as 'spam'.
On Mo
$ grep -i maintainer nvidia-driver.info
MAINTAINER="ppr:kut"
More appropriate than spamming the entire list.
On Mon, May 5, 2008 at 5:20 PM, Phillip Warner <[EMAIL PROTECTED]> wrote:
> "169.09" is hard coded in a line in nvidia-switch in the nvidia-driver
> slackBuild. The line should look like
"169.09" is hard coded in a line in nvidia-switch in the nvidia-driver
slackBuild. The line should look like the following instead:
/sbin/ldconfig -l /usr/lib/libGL.so.${NV_VERSION}-nvidia
--phil
-
Be a better friend, newshound, and know-it-all with Yaho
Hello,
I succeeded in compiling the mod2.6.24 version as tipped by Mauro Giachero.
Thanks again Mauro for the advise.
I didn't include the compiled r8187.ko module in my package as this module is
already in the kernel (rtl8187.ko) and I only needed the module for r8180
chipset.
Now I will monito
Iskar Enev wrote:
JK Wood wrote:
That's why I use these magic things called "folders" to keep track of
such things.
Imagine that for *some* reason you don't have the initial information -
how would you organize the folders then?
I also think it's a good idea to include the slackware version
And, at least for me, that's a "good thing". I make several small
changes to SBo scripts before I run them, including changing "#!/bin/sh"
to "#!/bin/bash" & removing the execute bit. My data partition is set up
nonexecutable & I want to keep it that way. I run the scripts with "bash
prgnam.Sla
JK Wood wrote:
That's why I use these magic things called "folders" to keep track of
such things.
Imagine that for *some* reason you don't have the initial information -
how would you organize the folders then?
I also think it's a good idea to include the slackware version in the
.info file
That's why I use these magic things called "folders" to keep track of such
things.
On Mon, May 5, 2008 at 10:17 AM, Phillip Warner <[EMAIL PROTECTED]> wrote:
> Even if you do have access to the repo it would be quicker to simply check
> the .info or .slackBuild file to see what slackware version
I know it isn't a requirement, I know what's in the HowTo, and I know how to
use chmod and sh. Personally, I could care less whether or not the execute
perms are there because if they aren't I just use sh. The only reason I
mentioned it is because there seemed to be some previous effort in get
Even if you do have access to the repo it would be quicker to simply check the
.info or .slackBuild file to see what slackware version it is for instead of
comparing it to what is in the repo. Either that, or people would just
download a fresh copy just to be sure (sometimes the program version
On Mon, May 5, 2008 at 3:11 PM, Ricardo Klein <[EMAIL PROTECTED]> wrote:
> Hi...
>
> I dont know if that is an error, but...sendin to you
>
> in eclipse.Slackbuild have this:
>
> # Add a script to run eclipse in /usr/bin
> mkdir -p $PKG/usr/bin
> cat $CWD/eclipse > $PKG/usr/bin/eclipse
>
>
Hi...
I dont know if that is an error, but...sendin to you
in eclipse.Slackbuild have this:
# Add a script to run eclipse in /usr/bin
mkdir -p $PKG/usr/bin
cat $CWD/eclipse > $PKG/usr/bin/eclipse
chmod 0755 $PKG/usr/bin/eclipse
But, only works for me if I put + "/eclipse" like that:
#
12 matches
Mail list logo
