Re: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0

2015-01-10 Thread King Beowulf 
On Friday, January 9, 2015, Thomas Szteliga t...@websafe.pl wrote:

 On 01/10/2015 12:48 AM, King Beowulf wrote:
  -current already has the new(er) libusb so there is no need to build a
  static version. The build system should pickup the system libusb.
  Don't forget to read the README!  Don't forget usbredir.

 Please check my

 http://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-January/013448.html

 spice-gtk (dependency of virt-manager) already requires usbredir
 so maybe usbredir should become a default for qemu?

 --
 Thomas Szteliga


Once -current goes stable, and we can dispense with the static lib stuff,
so we can revisit usbredir.



-- 
You! What PLANET is this!
-- McCoy, The City on the Edge of Forever, stardate 3134.0
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] rxvt-unicode up for grabs

2015-01-10 Thread LÉVAI Dániel 
On p, jan 02, 2015 at 15:31:24 +, Glenn Becker wrote:
 
 I'm not using it anymore. Anyone willing to take over?
 
 I'll adopt if no one else has beaten me ... :)
 

It's been two public update since. Is there anything else we supposed to
do to transfer maintainership?
Maybe a new update by the new maintainer? There is a new version -- just
saying.. :-)


Daniel

-- 
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D  650C C69B BE4C 83B6 3A8F
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Possible typo in python3.SlackBuild

2015-01-10 Thread Jim Diamond 
On Fri, Jan  9, 2015 at 20:45 (+0200), Audrius Kažukauskas wrote:

 On Fri, 2015-01-09 at 13:34:03 -0400, Jim Diamond wrote:
 On Fri, Jan  9, 2015 at 17:09 (+1000), Christoph Willing wrote:

 Its not stated there but I presume a blank offset defaults it to 0,
 therefore for a VERSION of 3.4.2, PYVER would be set to 3.4

 That is fragile code.  If VERSION got as high as 3.10.x, Bad Things
 would happen.

 Agreed, although very unlikely, according to one of Python
 developers[*]:

Also agreed.

Another problem with having fragile code is that it might propagate
itself into other Slackbuilds, which could (who knows?) end up with
that actually being a bug.

Cheers.

Jim
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] Possible typo in python3.SlackBuild

2015-01-10 Thread Christoph Willing 



On 01/11/2015 01:14 AM, Jim Diamond wrote:

On Fri, Jan  9, 2015 at 20:45 (+0200), Audrius Kažukauskas wrote:


On Fri, 2015-01-09 at 13:34:03 -0400, Jim Diamond wrote:

On Fri, Jan  9, 2015 at 17:09 (+1000), Christoph Willing wrote:



Its not stated there but I presume a blank offset defaults it to 0,
therefore for a VERSION of 3.4.2, PYVER would be set to 3.4



That is fragile code.  If VERSION got as high as 3.10.x, Bad Things
would happen.



Agreed, although very unlikely, according to one of Python
developers[*]:


Also agreed.

Another problem with having fragile code is that it might propagate
itself into other Slackbuilds, which could (who knows?) end up with
that actually being a bug.


If we're looking for something more robust, yet generic, then my 
previously proposed solution:

PYVER=${VERSION%.*}
is not so great if a version string has extra fields i.e. 
VERSION=3.4.2.5 would become 3.4.2 (rather than the desired 3.4).


To make up for that shortcoming, I offer:
PYVER=$(sed 's/\.[^\.]*//2g'  $VERSION)

Maybe not as easy to read as Audrius' solution using cut though ...

chris
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/