Re: [Slackbuilds-users] Fwd: AwesomeWM

2011-08-22 Thread Patrick J. Volkerding
On 08/22/2011 09:34 AM, Ben Mendis wrote: On Mon, Aug 22, 2011 at 10:14 AM, Gwenhael Le Moine gwenhael.le.mo...@gmail.com wrote: 2011/8/22 Arvydas Sidorenkoasi...@gmail.com: Hello, I don't know if this is a proper way to inform you this, but yeh, all is said below. Recent versions of

Re: [Slackbuilds-users] GoogleEarth Won't Start

2011-06-16 Thread Patrick J. Volkerding
On 06/16/2011 04:09 PM, David Spencer wrote: 2) Google Earth 6 is LSB compliant meaning it was built on a LSB system. Slackware however does not have that symlink which is part of the LSB 3.0 specification. You'll need to create the symlink manually after installing the package:

Re: [Slackbuilds-users] GConf and GORbit

2011-03-23 Thread Patrick J. Volkerding
On 03/23/2011 07:49 AM, Willy Sudiarto Raharjo wrote: Hi, GConf and GORbit are now included in -Current, so i guess it can be deleted from SBo ? I'm not so sure that they should be. I mean, I did try to hide them a bit -- they aren't just directory in /extra. Maybe there should be a

Re: [Slackbuilds-users] sse2 optimisation

2010-06-26 Thread Patrick J. Volkerding
On 06/26/2010 07:58 AM, David Spencer wrote: Greetings SlackPeople, may I ask your advice? I'm doing a SlackBuild for Luminance HDR. Its compiler flags assume that SSE2 instructions are available. That's a bad assumption, but it's easy to make it configurable with a variable SSE2=yes|no and a

Re: [Slackbuilds-users] 13.1

2010-05-25 Thread Patrick J. Volkerding
On 05/25/2010 10:30 PM, Robby Workman wrote: Anyway, since there seems to be some desire for a definitive statement on this, I'm going to make one: There are no plans to change the default package compression at any point in the near future. The reasons include, but are not necessarily limited

Re: [Slackbuilds-users] The plot thickens: A couple of 13.0 questions

2009-08-28 Thread Patrick J. Volkerding
Robby Workman wrote: On Fri, 28 Aug 2009 10:35:29 +0200 Morten Juhl-Johansen Zölde-Fejér mj...@syntaktisk.dk wrote: So, a new day, a new Slackware version. Have looked at the RCs - interesting changes. Let's see what we can make out of this one! Competition is strong - the 12.2 was a very good

Re: [Slackbuilds-users] Awesome window manager

2008-09-10 Thread Patrick J. Volkerding
cRaig Forrester wrote: On Wed, Sep 10, 2008 at 11:59 AM, Chess Griffin [EMAIL PROTECTED] wrote: The problem is, I've been using awesome for quite some now, and the developer has a history of completely rewriting the configuration file and making all sorts of substantial changes from one stable

Re: [Slackbuilds-users] Problem with Lilypond SlackBuild for 12.1

2008-08-31 Thread Patrick J. Volkerding
Robert W. Wendel wrote: Steve wrote: On Sunday 31 August 2008 05:20:52 pm Heinz Wiesinger wrote: Am Sonntag, 17. August 2008 22:09:16 schrieb Robert W. Wendel: I don't know where to post this so you see it but I'm having problems compiling lilypond. I get a compile error: WARNING:

Re: [Slackbuilds-users] bug in irqbalance

2008-08-31 Thread Patrick J. Volkerding
Grissiom wrote: Hi all, The irqbalance could only take into effect only if run as root. So here is my patch: Even if something only works for root, IMHO it is better to get upstream to make location changes. That way other things (scripts, perhaps) won't try to run with an absolute path of

Re: [Slackbuilds-users] tightvnc build script

2008-08-23 Thread Patrick J. Volkerding
Darrell Anderson wrote: Greetings, Recently I posted a request for help at LQ regarding the tightvnc slackbuild. Yes, I should have posted here and I was reminded at LQ for not doing that. My apologies. I do not maintain a full install of Slackware. Through the LQ discussion

Re: [Slackbuilds-users] make -j4 [was: linuxwacom slackbuild]

2008-08-08 Thread Patrick J. Volkerding
Murat D. Kadirov wrote: My example :) My laptop with Celeron 1.4Ghz and 256Mb RAM with -j 2 compile corrupted binary file djview3 (djvulibre package). It's a known issue that djvulibre does not handle parallel builds. This isn't due to lack of memory or CPU horsepower...