Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

I've not tried with plus sign. I've tested - find ... -print0 | xargs -0 ... - find ... -exec 755 {} \; - find ... -execdir 755 {} \; Last two forms required like ten times more time than first one. On MAME case, it's a huge amount of time. Em 14 de 03 de 2016 às 20:32:44T-0500, Kyle Guinn

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

On 3/14/16, Didier Spaier wrote: > Let me add: only make a change if there is a proven advantage, like > _ old way failing (provide example), where the new one does not I occasionally come across source tarballs where every file unintentionally has the sticky bit set. (I don't

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

On 3/14/16, Luís Fernando Carvalho Cavalheiro wrote: > Hey guys. As ironic it looks like, the fastest approach is find + xargs. I > won't rewrite my own SlackBuilds, but new ones will use find + xargs. Have you tried "-exec chmod 644 {} +" or "-execdir chmod 644 {} +"

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

Hey guys. As ironic it looks like, the fastest approach is find + xargs. I won't rewrite my own SlackBuilds, but new ones will use find + xargs. Em 14 de 03 de 2016 às 15:48:55T-0500, Erik Hanson escreveu: > On Mon, 14 Mar 2016 16:04:50 -0300 > Luis Cavalheiro

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

I'm with -execdir approach. I use it on my personal slackbuild scripts (hosted at https://github.com/lcavalheiro/slackbuilds - I plan to submit them to http://slackbuilds.org as soon as submissions are allowed again), and all of them build very well :-) I'm testing the tree approaches (find +

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

On Mon, 14 Mar 2016 16:04:50 -0300 Luis Cavalheiro wrote: > Indeed it should be > > -execdir chmod 755 {} \; > > ...at end of command line. I was fast typing and I did this little > mistake. As said, command will stop in error in "-print0 | xargs -0" > form if no

Re: [Slackbuilds-users] new nvidia 361.28 ready for testing.

here I applied this small diff to nvidia-switch to make ldconfig happy. --- nvidia-switch.orig 2016-03-13 06:13:38.0 +0100 +++ nvidia-switch 2016-03-14 21:09:40.956989151 +0100 @@ -56,17 +56,20 @@ if [ -e libEGL.so.1.0.0 ]; then mv libEGL.so.1.0.0 libEGL.so.1.0.0-xorg

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

Indeed it should be -execdir chmod 755 {} \; ...at end of command line. I was fast typing and I did this little mistake. As said, command will stop in error in "-print0 | xargs -0" form if no matching file is provided. Plus, since the sole function of this piped xargs is chmod, it is an uneeded

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

On 14/03/2016 18:29, Erik Hanson wrote: > Didier Spaier wrote: > >> Maybe it wouldn't hurt to write >> -execdir 755 > > Unless I'm misunderstanding the man page, this would need to be > -execdir chmod 755 {} \; Indeed, sorry for the mistake. Didier 0x60C03EEA.asc

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

On Mon, 14 Mar 2016 17:50:39 +0100 Didier Spaier wrote: > Maybe it wouldn't hurt to write > -execdir 755 Unless I'm misunderstanding the man page, this would need to be -execdir chmod 755 {} \; It seems like there's possible value there, and it doesn't deviate too far from

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

On 14/03/2016 13:39, Bryan Harris wrote: > Why worry so much over something so insignificant? Just do whatever > Volkerding does. +1. Let me add: only make a change if there is a proven advantage, like _ old way failing (provide example), where the new one does not _ new way *significantly*

Re: [Slackbuilds-users] Keepassx

> I've just updated keepassx to 2.0.2 and tested it under current. I > don't know if it is ok for the maintainer. I attach a git patch. I can > make a pull request if needed. pushed to my branch -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature

Re: [Slackbuilds-users] Server maintenance

On Mon, Mar 14, 2016 at 10:48:11AM -0500, Robby Workman wrote: > Because harrier hosts the SBo mailing lists, MX, and DNS, expect > those things to be inaccessible for a bit. http, ftp, and rsync > access to the SBo repo should be unaffected. DNS will only be slightly affected, not noticed by the

Re: [Slackbuilds-users] Brief interruption in service at lists.slackbuilds.org, 2016-03-17

On Mon, 14 Mar 2016 10:44:46 -0500 Rob McGee wrote: > Robby and I will be doing a hardware upgrade on harrier, the machine > which hosts lists.slackbuilds.org, probably on Thursday this week. > We're going to try filling it with green beer to see if that will > improve

Re: [Slackbuilds-users] Brief interruption in service at lists.slackbuilds.org, 2016-03-17

Shame it would be at Alabama... Or shame on me for being at Brazil at this moment :-) Em 14/03/2016 12:44 PM, "Rob McGee" escreveu: > Robby and I will be doing a hardware upgrade on harrier, the machine > which hosts lists.slackbuilds.org, probably on Thursday this week. >

[Slackbuilds-users] Server maintenance

At some point on Thursday, 20160317 (probably sometime between 1500 and 2100 UTC), harrier.slackbuilds.org will be temporarily shut down for some minor maintenance work - we'll be replacing a couple of hard drives and adding another to the raid array. Because harrier hosts the SBo mailing lists,

[Slackbuilds-users] Brief interruption in service at lists.slackbuilds.org, 2016-03-17

Robby and I will be doing a hardware upgrade on harrier, the machine which hosts lists.slackbuilds.org, probably on Thursday this week. We're going to try filling it with green beer to see if that will improve performance. If that fails, we'll fill ourselves with green beer and revert

Re: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs

2016-03-13 23:30 GMT+01:00 Willy Sudiarto Raharjo : >> Are you guys up to date with the Thu Mar 10 02:46:49 UTC 2016 -current >> update? > > Yes, my system is up to date with latest current update, but probably > since i tested in my desktop, it's also filled with many

[Slackbuilds-users] Keepassx

Hello, I've just updated keepassx to 2.0.2 and tested it under current. I don't know if it is ok for the maintainer. I attach a git patch. I can make a pull request if needed. regards Eugene diff --git a/office/keepassx/keepassx-0.4.3-gcc47.patch b/office/keepassx/keepassx-0.4.3-gcc47.patch

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

Why worry so much over something so insignificant? Just do whatever Volkerding does. https://en.wikipedia.org/wiki/Perfect_is_the_enemy_of_good On Mon, Mar 14, 2016 at 2:00 AM, Franzen wrote: > On 2016-03-13 20:00, Andrzej Telszewski wrote: > >> On 13/03/16 19:46,

Re: [Slackbuilds-users] Updating slackbuilds

2016-03-14 7:31 GMT+01:00 Eric Pratt : > I see. Thanks! > > On Sun, Mar 13, 2016 at 11:02 PM, Willy Sudiarto Raharjo > wrote: >> >> > Well, it looks like the same guy did it again in January. I thought >> > only >> > the maintainer could submit

Re: [Slackbuilds-users] Updating slackbuilds

I see. Thanks! On Sun, Mar 13, 2016 at 11:02 PM, Willy Sudiarto Raharjo < will...@slackbuilds.org> wrote: > > Well, it looks like the same guy did it again in January. I thought only > > the maintainer could submit updates to the slackbuild. Is that > incorrect? > > > > Since this appears to

Re: [Slackbuilds-users] Updating slackbuilds

> Well, it looks like the same guy did it again in January. I thought only > the maintainer could submit updates to the slackbuild. Is that incorrect? > > Since this appears to be happening, lets just go ahead and commit this > update. It eliminates the cumbersome patch files and gets us all

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

On 2016-03-13 20:00, Andrzej Telszewski wrote: On 13/03/16 19:46, Ryan P.C. McQuen wrote: On Sun, Mar 13, 2016 at 11:36 AM Andrzej Telszewski > wrote: On 13/03/16 19:29, Luís Fernando Carvalho Cavalheiro wrote: > Well, well...