From qwiat at o2.pl  Sun Nov  1 01:31:29 2009
From: qwiat at o2.pl (Pawel Kwiatkowski)
Date: Sun, 01 Nov 2009 01:31:29 +0100
Subject: packages/apache/apache.spec - diff - 1.578
In-Reply-To: <200910301718.25457.glen@pld-linux.org>
References: <200910301718.25457.glen@pld-linux.org>
Message-ID: <1257035489.8518.14.camel@localhost>

Dnia 2009-10-30, pi? o godzinie 18:18 +0300, Elan Ruusam?e pisze:
> http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/packages/apache/apache.spec.diff?r1=1.577;r2=1.578;f=h
> 
> could it be like described what for this requirement was raised?

New apache don't work with older openssl. Startup failed with missing
symbols. I'm sorry that i wrote so short info about this change.


-- 
Pawe? Kwiatkowski
e-mail/jid: qwiat(at)pld-linux(dot)org



From glen at pld-linux.org  Mon Nov  2 10:49:23 2009
From: glen at pld-linux.org (Elan =?utf-8?q?Ruusam=C3=A4e?=)
Date: Mon, 2 Nov 2009 12:49:23 +0300
Subject: packages/apache/apache.spec - diff - 1.578
In-Reply-To: <1257035489.8518.14.camel@localhost>
References: <200910301718.25457.glen@pld-linux.org>
	<1257035489.8518.14.camel@localhost>
Message-ID: <200911021149.23553.glen@pld-linux.org>

On Sunday 01 November 2009 02:31:29 Pawel Kwiatkowski wrote:
> Dnia 2009-10-30, pi? o godzinie 18:18 +0300, Elan Ruusam?e pisze:
> > http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/packages/apache/apache.spec.d
> >iff?r1=1.577;r2=1.578;f=h
> >
> > could it be like described what for this requirement was raised?
>
> New apache don't work with older openssl. Startup failed with missing
> symbols. I'm sorry that i wrote so short info about this change.

um, it just means it needed exact openssl version used for build... ABI 
changed unexpectedly?, should SONAME had been increased instead?

any details what the error was?

-- 
glen


From glen at pld-linux.org  Mon Nov  2 10:51:53 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Mon, 2 Nov 2009 12:51:53 +0300
Subject: packages: phpMyAdmin/phpMyAdmin.spec - no php application
	requires mod_php, ...
In-Reply-To: <packages_phpMyAdmin_phpMyAdmin.spec.1.219@pld-linux.org>
References: <packages_phpMyAdmin_phpMyAdmin.spec.1.218@pld-linux.org>
	<packages_phpMyAdmin_phpMyAdmin.spec.1.219@pld-linux.org>
Message-ID: <200911021151.53897.glen@pld-linux.org>

On Saturday 31 October 2009 00:57:08 shadzik wrote:
> packages/phpMyAdmin/phpMyAdmin.spec:1.219 ---
> packages/phpMyAdmin/phpMyAdmin.spec:1.218	Fri Oct 30 23:55:04 2009 +++
> packages/phpMyAdmin/phpMyAdmin.spec	Fri Oct 30 23:57:03 2009
> @@ -27,7 +27,7 @@
>  Requires:	webapps
>  Requires:	webserver(access)
>  Requires:	webserver(alias)
> -Requires:	webserver(php)
> +Suggests:	webserver(php)
>  Suggests:	php-mysqli
>  Suggests:	webserver(indexfile)
>  BuildArch:	noarch
> @@ -157,6 +157,9 @@
>  All persons listed below can be reached at <cvs_login>@pld-linux.org
>
>  $Log$
> +Revision 1.219  2009/10/30 22:57:03  shadzik
> +- no php application requires mod_php, so just suggest it, it's no
> requirement at all

what you mean?

it runs on cli mode?

so you should change the other webserver(xxx) to suggests too!

-- 
glen


From gotar at polanet.pl  Mon Nov  2 10:59:10 2009
From: gotar at polanet.pl (Tomasz Pala)
Date: Mon, 2 Nov 2009 10:59:10 +0100
Subject: packages/apache/apache.spec - diff - 1.578
In-Reply-To: <200911021149.23553.glen@pld-linux.org>
References: <200910301718.25457.glen@pld-linux.org>
	<1257035489.8518.14.camel@localhost>
	<200911021149.23553.glen@pld-linux.org>
Message-ID: <20091102095909.GA1997@polanet.pl>

On Mon, Nov 02, 2009 at 12:49:23 +0300, Elan Ruusam?e wrote:

>> New apache don't work with older openssl. Startup failed with missing
>> symbols. I'm sorry that i wrote so short info about this change.
> 
> um, it just means it needed exact openssl version used for build... ABI 
> changed unexpectedly?, should SONAME had been increased instead?

No, not necessarily - probably just new symbols has been added.

-- 
Tomasz Pala <gotar at pld-linux.org>


From glen at pld-linux.org  Mon Nov  2 11:29:45 2009
From: glen at pld-linux.org (Elan =?utf-8?q?Ruusam=C3=A4e?=)
Date: Mon, 2 Nov 2009 13:29:45 +0300
Subject: packages: phpMyAdmin/phpMyAdmin.spec - no php application
	requires mod_php, ...
In-Reply-To: <ed7233d50911020203q938dd77g49ae5e6a5e715e36@mail.gmail.com>
References: <packages_phpMyAdmin_phpMyAdmin.spec.1.218@pld-linux.org>
	<200911021151.53897.glen@pld-linux.org>
	<ed7233d50911020203q938dd77g49ae5e6a5e715e36@mail.gmail.com>
Message-ID: <200911021229.46039.glen@pld-linux.org>

On Monday 02 November 2009 12:03:29 Bartosz ?wi?tek wrote:
> 2009/11/2 Elan Ruusam?e <glen at pld-linux.org>:
> > On Saturday 31 October 2009 00:57:08 shadzik wrote:
> >> packages/phpMyAdmin/phpMyAdmin.spec:1.219 ---
> >> packages/phpMyAdmin/phpMyAdmin.spec:1.218 ? ? Fri Oct 30 23:55:04 2009
> >> +++ packages/phpMyAdmin/phpMyAdmin.spec ? Fri Oct 30 23:57:03 2009
> >> @@ -27,7 +27,7 @@
> >> ?Requires: ? ?webapps
> >> ?Requires: ? ?webserver(access)
> >> ?Requires: ? ?webserver(alias)
> >> -Requires: ? ?webserver(php)
> >> +Suggests: ? ?webserver(php)
> >> ?Suggests: ? ?php-mysqli
> >> ?Suggests: ? ?webserver(indexfile)
> >> ?BuildArch: ? noarch
> >> @@ -157,6 +157,9 @@
> >> ?All persons listed below can be reached at <cvs_login>@pld-linux.org
> >>
> >> ?$Log$
> >> +Revision 1.219 ?2009/10/30 22:57:03 ?shadzik
> >> +- no php application requires mod_php, so just suggest it, it's no
> >> requirement at all
> >
> > what you mean?
> >
> > it runs on cli mode?
>
> Sure.
so instead create subpackage for -cli and -web mode?

> > so you should change the other webserver(xxx) to suggests too!
>
> Why is that? I just say mod_php isn't required, not that mod_alias or
> other equivalents aren't.

if you intend to run it without webserver (cli mode), then why require 
webserver packages??

or what are you trying to acomplish? describe your (wanted) setup?

and seems you don't know that webserver(php) is not apaache centric maybe that 
is your problem?

$ ac-provides 'webserver(php)'
apache-mod_php-5.2.11-2.amd64
apache-mod_php-5.2.1-6.amd64
apache-mod_php4-4.4.9-12.amd64
apache-mod_php4-4.4.6-4.amd64
apache1-mod_php-5.2.11-2.amd64
apache1-mod_php-5.2.1-6.amd64
apache1-mod_php4-4.4.9-12.amd64
apache1-mod_php4-4.4.6-4.amd64
lighttpd-mod_cgi_php-1.4.24-1.amd64
lighttpd-php-spawned-1.4.24-1.amd64
php-fcgi-5.2.11-2.amd64
php-fcgi-5.2.1-6.amd64
php-fpm-5.2.11-2.amd64
php4-fcgi-4.4.9-12.amd64
php4-fcgi-4.4.6-4.amd64


-- 
glen


From glen at pld-linux.org  Mon Nov  2 14:08:59 2009
From: glen at pld-linux.org (Elan =?utf-8?q?Ruusam=C3=A4e?=)
Date: Mon, 2 Nov 2009 16:08:59 +0300
Subject: packages: phpMyAdmin/phpMyAdmin.spec - no php application
	requires mod_php, ...
In-Reply-To: <ed7233d50911020408s196ddd81ub2ad3b1d3488cab@mail.gmail.com>
References: <packages_phpMyAdmin_phpMyAdmin.spec.1.218@pld-linux.org>
	<200911021229.46039.glen@pld-linux.org>
	<ed7233d50911020408s196ddd81ub2ad3b1d3488cab@mail.gmail.com>
Message-ID: <200911021509.00158.glen@pld-linux.org>

On Monday 02 November 2009 14:08:37 Bartosz ?wi?tek wrote:
> >
> > it runs on cli mode?
>
> Sure.

seems you don't understand what CLI is, do you? you're constantly referring 
back to webserver.

> > and seems you don't know that webserver(php) is not apaache centric maybe
> > that is your problem?
> >
> > $ ac-provides 'webserver(php)'
> > apache-mod_php-5.2.11-2.amd64
> > apache-mod_php-5.2.1-6.amd64
> > apache-mod_php4-4.4.9-12.amd64
> > apache-mod_php4-4.4.6-4.amd64
> > apache1-mod_php-5.2.11-2.amd64
> > apache1-mod_php-5.2.1-6.amd64
> > apache1-mod_php4-4.4.9-12.amd64
> > apache1-mod_php4-4.4.6-4.amd64
> > lighttpd-mod_cgi_php-1.4.24-1.amd64
> > lighttpd-php-spawned-1.4.24-1.amd64
> > php-fcgi-5.2.11-2.amd64
> > php-fcgi-5.2.1-6.amd64
> > php-fpm-5.2.11-2.amd64
> > php4-fcgi-4.4.9-12.amd64
> > php4-fcgi-4.4.6-4.amd64
>
> Hmm, i'm running php as cgi, with cgiwrap, so I just need php-cgi to
> run phpMyAdmin. By default it installed apache-mod_php which isn't
> needed at all in my configuration - therefore the change. But of
> course I use "Alias" in the config for myadmin etc. so other apache
> modules make sens to me. I guess if you run lighttpd or nginx you
> won't use mod_php either... this change makes sense to me, but if
> there's something I didn't think about feel free to correct me.

so create similar package for apache like there exists lighttpd-mod_cgi_php.

-- 
glen


From glen at pld-linux.org  Mon Nov  2 15:17:22 2009
From: glen at pld-linux.org (Elan =?utf-8?q?Ruusam=C3=A4e?=)
Date: Mon, 2 Nov 2009 17:17:22 +0300
Subject: packages: phpMyAdmin/phpMyAdmin.spec - no php application
	requires mod_php, ...
In-Reply-To: <ed7233d50911020552s2ba866bp49ef4408b5e54a59@mail.gmail.com>
References: <packages_phpMyAdmin_phpMyAdmin.spec.1.218@pld-linux.org>
	<200911021509.00158.glen@pld-linux.org>
	<ed7233d50911020552s2ba866bp49ef4408b5e54a59@mail.gmail.com>
Message-ID: <200911021617.22707.glen@pld-linux.org>

On Monday 02 November 2009 15:52:04 Bartosz ?wi?tek wrote:
> Well, I haven't checked, but it seems to me that this is a macro which
> describes all possible webserver - am I right? And I still tend to the
> opinion that phpMyAdmin does not need webserver(php) to run - as this
> means mod_php - I haven't had any other poldek-guess so I again assume
> I'm right :)

no, it does NOT mean mod_php. look again the previous email(s), it matches 
cgi, fcgi and various other packages.

it means something that provides the PHP ENGINE:

http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/packages/webapps/webapps.README

> Why do I need to do this subpackage which will only be a metapackage
> (I guess) when it also works without it only by suggesting
> webserver(php)? I don't get the idea behind this. Instead of
> installing a metapackage just to satisfy RPM/Poldek I can leave that
> empty and be perfectly happy without it, right? :)

not really, the metapackage has also requirement for other dependencies, like 
the mod_cgi to be able to run. really. make similar metapackage as lighttpd 
has.

-- 
glen


From arekm at maven.pl  Wed Nov  4 10:21:37 2009
From: arekm at maven.pl (Arkadiusz Miskiewicz)
Date: Wed, 4 Nov 2009 10:21:37 +0100
Subject: packages: util-vserver/util-vserver-initpost.sh - don't set
	RPM_SKIP_AUTO_R...
In-Reply-To: <packages_util_vserver_util_vserver_initpost.sh.1.3@pld-linux.org>
References: <packages_util_vserver_util_vserver_initpost.sh.1.2@pld-linux.org>
	<packages_util_vserver_util_vserver_initpost.sh.1.3@pld-linux.org>
Message-ID: <200911041021.37582.arekm@maven.pl>

On Wednesday 04 of November 2009, blues wrote:
> Author: blues                        Date: Wed Nov  4 08:43:35 2009 GMT

> +
> +	# pam_limits causes problems
> +	#
>  http://linux-vserver.org/Frequently_Asked_Questions#When_using_nice_and_su
> _.28for_example.2C_in_the_updatedb_cron_job.29.2C_I_get:_su:_Permission_den
> ied._What_does_it_mean.3F +	for file in /etc/pam.d/*; do
> +		subst ${file} 's!^\([^#].*pam_limits.so\)!#\1!'
> +	done

Are you drunk?!

I _need_ limits for services in my vpses. Fix your systems and don't break 
default configuration.

-- 
Arkadiusz Mi?kiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/


From glen at pld-linux.org  Fri Nov  6 13:11:52 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Fri, 6 Nov 2009 14:11:52 +0200
Subject: keyword subst
In-Reply-To: <200901131859.20663.glen@pld-linux.org>
References: <200901131859.20663.glen@pld-linux.org>
Message-ID: <200911061411.52662.glen@pld-linux.org>

On Tuesday 13 January 2009 18:59:20 Elan Ruusam?e wrote:
> could anyone describe how do you actually disable keyword subst with cvsnt?
>
> glen at builder-ac pld/SOURCES $ grep 7.2.072 CVS/Entries
> /7.2.072/1.3/Tue Jan 13 16:57:33 2009/-ko/
> glen at builder-ac pld/SOURCES $ rm 7.2.072
> glen at builder-ac pld/SOURCES $ cvs up 7.2.072
> U 7.2.072
> glen at builder-ac pld/SOURCES $ grep 7.2.072 CVS/Entries
> /7.2.072/1.3/Tue Jan 13 16:58:12 2009/-kkv/
> (reverse-i-search)`cvs up ': cvs up spec.vim
> glen at builder-ac pld/SOURCES $ cvs update -ko 7.2.072
> U 7.2.072
> glen at builder-ac pld/SOURCES $ cvs ci -f -m '- disable keyword subst'
> 7.2.072 cvs server: Up-to-date check failed for `7.2.072'
> cvs [server aborted]: correct above errors first!

seems it could work only if client is too cvsnt.

however still failed even with the doc described here:
http://www.cvsnt.org/manual/html/Substitution-modes.html

client version: cvsnt-2.5.04.3510-1.x86_64
tested file: packages/varnish/branch.diff

fcking shit not cvs client/server

-- 
glen


From glen at pld-linux.org  Fri Nov  6 15:19:36 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Fri, 6 Nov 2009 16:19:36 +0200
Subject: keyword subst
In-Reply-To: <200911061411.52662.glen@pld-linux.org>
References: <200901131859.20663.glen@pld-linux.org>
	<200911061411.52662.glen@pld-linux.org>
Message-ID: <200911061619.36184.glen@pld-linux.org>

On Friday 06 November 2009 14:11:52 Elan Ruusam?e wrote:
> however still failed even with the doc described here:
> http://www.cvsnt.org/manual/html/Substitution-modes.html

hmm, seems it is still possible if done from scratch:

short moral:
cvs up -ko FILE
cvs ci -f -m "blah" FILE

$ PS1='$ '
$ cp keywords.diff~ keywords.diff~~~
$ cvs add keywords.diff~~~
cvs server: scheduling file `keywords.diff~~~' for addition
cvs server: use 'cvs commit' to add this file permanently
$ cvs ci -f -m '- x' keywords.diff~~~
RCS file: /cvsroot/test/keywords.diff~~~,v
done
Checking in keywords.diff~~~;
/cvsroot/test/keywords.diff~~~,v  <--  keywords.diff~~~
initial revision: 1.1
done
$ cvs status -v keywords.diff~~~
===================================================================
File: keywords.diff~~~  Status: Up-to-date

   Working revision:    1.1
   Repository revision: 1.1     /cvsroot/test/keywords.diff~~~,v
   Expansion option:    kv
   Commit Identifier:   43f84af42fec1604
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)
   Merge From:          (none)

   Existing Tags:
        No Tags Exist

$ cat keywords.diff~~~
# $Revision: 1.1 $, $Date: 2009/11/06 14:17:17 $
Summary:        Just a drink
$ cvs ci -f -m '- x' keywords.diff~~~
Checking in keywords.diff~~~;
/cvsroot/test/keywords.diff~~~,v  <--  keywords.diff~~~
new revision: 1.2; previous revision: 1.1
done
$ cat keywords.diff~~~
# $Revision: 1.2 $, $Date: 2009/11/06 14:17:36 $
Summary:        Just a drink
$ cvs up -ko keywords.diff~~~
U keywords.diff~~~
$ cvs ci -f -m '- x' keywords.diff~~~
Checking in keywords.diff~~~;
/cvsroot/test/keywords.diff~~~,v  <--  keywords.diff~~~
new revision: 1.3; previous revision: 1.2
done
$ cat keywords.diff~~~
# $Revision: 1.1 $, $Date: 2009/11/06 14:17:17 $
Summary:        Just a drink
$ cvs status -v keywords.diff~~~
===================================================================
File: keywords.diff~~~  Status: Up-to-date

   Working revision:    1.3
   Repository revision: 1.3     /cvsroot/test/keywords.diff~~~,v
   Expansion option:    o
   Commit Identifier:   453c4af4301391ea
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      o
   Merge From:          (none)

   Existing Tags:
        No Tags Exist



-- 
glen


From freetz at gmx.net  Fri Nov  6 18:29:31 2009
From: freetz at gmx.net (Fryderyk Dziarmagowski)
Date: Fri, 6 Nov 2009 18:29:31 +0100
Subject: packages: gnome-control-center/gnome-control-center.spec - BR:
	desktop-file...
In-Reply-To: <packages_gnome_control_center_gnome_control_center.spec.1.29@pld-linux.org>
References: <packages_gnome_control_center_gnome_control_center.spec.1.28@pld-linux.org>
	<packages_gnome_control_center_gnome_control_center.spec.1.29@pld-linux.org>
Message-ID: <20091106182931.5cbdd7ad.freetz@gmx.net>

On Fri, 06 Nov 2009 16:43:25 +0100
sls <sls at pld-linux.org> wrote:

> Author: sls                          Date: Fri Nov  6 15:43:25 2009 GMT
> Module: packages                      Tag: HEAD
> ---- Log message:
> - BR: desktop-file-utils

this is runtime dependency.
https://bugzilla.gnome.org/show_bug.cgi?id=575278

-- 
freetz


From qboosh at pld-linux.org  Fri Nov  6 23:08:22 2009
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Fri, 6 Nov 2009 23:08:22 +0100
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <packages_secpanel_TODO.1.1@pld-linux.org>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<packages_secpanel_TODO.NONE@pld-linux.org>
	<packages_secpanel_TODO.1.1@pld-linux.org>
Message-ID: <20091106220822.GC26745@stranger.qboosh.pl>

On Thu, Oct 29, 2009 at 09:15:20AM +0100, blues wrote:
> Author: blues                        Date: Thu Oct 29 08:15:20 2009 GMT
> Module: packages                      Tag: HEAD
> ---- Log message:
> - TODO
> 
> ---- Files affected:
> packages/secpanel:
>    secpanel.spec (1.31 -> 1.32) , TODO (NONE -> 1.1)  (NEW)
> 
> ---- Diffs:
> 
> ================================================================
> Index: packages/secpanel/secpanel.spec
> diff -u packages/secpanel/secpanel.spec:1.31 packages/secpanel/secpanel.spec:1.32
> --- packages/secpanel/secpanel.spec:1.31	Fri Apr 10 10:39:10 2009
> +++ packages/secpanel/secpanel.spec	Thu Oct 29 09:15:14 2009
> @@ -1,6 +1,4 @@
>  # $Revision$, $Date$
> -# TODO:
> -# - some icon for desktop
>  Summary:	Visual management of SSH connections
>  Summary(pl.UTF-8):	Wizualna nak?adka na klienta SSH
>  Name:		secpanel

> ================================================================
> Index: packages/secpanel/TODO
> diff -u /dev/null packages/secpanel/TODO:1.1
> --- /dev/null	Thu Oct 29 09:15:20 2009
> +++ packages/secpanel/TODO	Thu Oct 29 09:15:14 2009
> @@ -0,0 +1,2 @@
> +# TODO:
> +- some icon for desktop
> ================================================================

I don't find such way useful:
- when I download package by builder, I don't have ANY idea, that there
  even is any TODO
- TODO is not available in .src.rpm


-- 
Jakub Bogusz    http://qboosh.pl/


From baggins at sith.mimuw.edu.pl  Sat Nov  7 16:56:00 2009
From: baggins at sith.mimuw.edu.pl (Jan Rekorajski)
Date: Sat, 7 Nov 2009 16:56:00 +0100
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <20091106220822.GC26745@stranger.qboosh.pl>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<packages_secpanel_TODO.NONE@pld-linux.org>
	<packages_secpanel_TODO.1.1@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
Message-ID: <20091107155600.GB12086@sith.mimuw.edu.pl>

On Fri, 06 Nov 2009, Jakub Bogusz wrote:

> On Thu, Oct 29, 2009 at 09:15:20AM +0100, blues wrote:
> > Author: blues                        Date: Thu Oct 29 08:15:20 2009 GMT
> > Module: packages                      Tag: HEAD
> > ---- Log message:
> > - TODO
> > 
> > ---- Files affected:
> > packages/secpanel:
> >    secpanel.spec (1.31 -> 1.32) , TODO (NONE -> 1.1)  (NEW)
[...]
> 
> I don't find such way useful:
> - when I download package by builder, I don't have ANY idea, that there
>   even is any TODO
> - TODO is not available in .src.rpm

I second that. Blues please stop making this mess.

-- 
Jan Rekorajski            |  ALL SUSPECTS ARE GUILTY. PERIOD!
baggins<at>mimuw.edu.pl   |  OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
BOFH, MANIAC              |                   -- TROOPS by Kevin Rubio


From blues at pld-linux.org  Sat Nov  7 17:47:48 2009
From: blues at pld-linux.org (Pawel Golaszewski)
Date: Sat, 7 Nov 2009 17:47:48 +0100 (CET)
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <20091106220822.GC26745@stranger.qboosh.pl>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<packages_secpanel_TODO.NONE@pld-linux.org>
	<packages_secpanel_TODO.1.1@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
Message-ID: <alpine.LNX.2.00.0911071743030.17150@fgnss.gnfx.tqn.cy>

On Fri, 6 Nov 2009, Jakub Bogusz wrote:
> > Author: blues                        Date: Thu Oct 29 08:15:20 2009 GMT
> > Module: packages                      Tag: HEAD
> > ---- Log message:
> > - TODO
> > 
> > ---- Files affected:
> > packages/secpanel:
> >    secpanel.spec (1.31 -> 1.32) , TODO (NONE -> 1.1)  (NEW)
> > 
> > ---- Diffs:
> > 
> > ================================================================
> > Index: packages/secpanel/secpanel.spec
> > diff -u packages/secpanel/secpanel.spec:1.31 packages/secpanel/secpanel.spec:1.32
> > --- packages/secpanel/secpanel.spec:1.31	Fri Apr 10 10:39:10 2009
> > +++ packages/secpanel/secpanel.spec	Thu Oct 29 09:15:14 2009
> > @@ -1,6 +1,4 @@
> >  # $Revision$, $Date$
> > -# TODO:
> > -# - some icon for desktop
> >  Summary:	Visual management of SSH connections
> >  Summary(pl.UTF-8):	Wizualna nak?adka na klienta SSH
> >  Name:		secpanel
> 
> > ================================================================
> > Index: packages/secpanel/TODO
> > diff -u /dev/null packages/secpanel/TODO:1.1
> > --- /dev/null	Thu Oct 29 09:15:20 2009
> > +++ packages/secpanel/TODO	Thu Oct 29 09:15:14 2009
> > @@ -0,0 +1,2 @@
> > +# TODO:
> > +- some icon for desktop
> > ================================================================
> I don't find such way useful:

I do.
You can put there a lot more info that in spec header, without any "^#". 
Compilation errors, whatever.

I never liked long TODO's in spec headers. It's only noise.

> - when I download package by builder, I don't have ANY idea, that there
>   even is any TODO

True - it should be fixed.

> - TODO is not available in .src.rpm

It can be packaged as doc. Easy to do. Packaging it and putting as Source 
will fix previous issue...

-- 
pozdr.  Pawe? Go?aszewski          jid:blues<at>jabber<dot>gda<dot>pl
--------------------------------------------------------------------------
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby
Pro-Logic Surround Sound with Bass Boost and all the music is free.

From blues at pld-linux.org  Sat Nov  7 17:57:11 2009
From: blues at pld-linux.org (Pawel Golaszewski)
Date: Sat, 7 Nov 2009 17:57:11 +0100 (CET)
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <20091107155600.GB12086@sith.mimuw.edu.pl>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<packages_secpanel_TODO.NONE@pld-linux.org>
	<packages_secpanel_TODO.1.1@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
	<20091107155600.GB12086@sith.mimuw.edu.pl>
Message-ID: <alpine.LNX.2.00.0911071756420.17150@fgnss.gnfx.tqn.cy>

On Sat, 7 Nov 2009, Jan Rekorajski wrote:
> > > Author: blues                        Date: Thu Oct 29 08:15:20 2009 GMT
> > > Module: packages                      Tag: HEAD
> > > ---- Log message:
> > > - TODO
> > > 
> > > ---- Files affected:
> > > packages/secpanel:
> > >    secpanel.spec (1.31 -> 1.32) , TODO (NONE -> 1.1)  (NEW)
> [...]
> > I don't find such way useful:
> > - when I download package by builder, I don't have ANY idea, that there
> >   even is any TODO
> > - TODO is not available in .src.rpm
> I second that. Blues please stop making this mess.

TODOs in spec is a mess...

-- 
pozdr.  Pawe? Go?aszewski          jid:blues<at>jabber<dot>gda<dot>pl
--------------------------------------------------------------------------
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby
Pro-Logic Surround Sound with Bass Boost and all the music is free.

From arekm at maven.pl  Sat Nov  7 18:32:21 2009
From: arekm at maven.pl (Arkadiusz Miskiewicz)
Date: Sat, 7 Nov 2009 18:32:21 +0100
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <20091107155600.GB12086@sith.mimuw.edu.pl>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
	<20091107155600.GB12086@sith.mimuw.edu.pl>
Message-ID: <200911071832.21803.arekm@maven.pl>

On Saturday 07 of November 2009, Jan Rekorajski wrote:
> On Fri, 06 Nov 2009, Jakub Bogusz wrote:
> > On Thu, Oct 29, 2009 at 09:15:20AM +0100, blues wrote:
> > > Author: blues                        Date: Thu Oct 29 08:15:20 2009 GMT
> > > Module: packages                      Tag: HEAD
> > > ---- Log message:
> > > - TODO
> > >
> > > ---- Files affected:
> > > packages/secpanel:
> > >    secpanel.spec (1.31 -> 1.32) , TODO (NONE -> 1.1)  (NEW)
> 
> [...]
> 
> > I don't find such way useful:
> > - when I download package by builder, I don't have ANY idea, that there
> >   even is any TODO
> > - TODO is not available in .src.rpm
> 
> I second that. Blues please stop making this mess.

Me too.

-- 
Arkadiusz Mi?kiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/


From gotar at polanet.pl  Sat Nov  7 18:34:39 2009
From: gotar at polanet.pl (Tomasz Pala)
Date: Sat, 7 Nov 2009 18:34:39 +0100
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <200911071832.21803.arekm@maven.pl>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
	<20091107155600.GB12086@sith.mimuw.edu.pl>
	<200911071832.21803.arekm@maven.pl>
Message-ID: <20091107173439.GA19608@polanet.pl>

On Sat, Nov 07, 2009 at 18:32:21 +0100, Arkadiusz Miskiewicz wrote:

>> I second that. Blues please stop making this mess.
> 
> Me too.

+1

-- 
Tomasz Pala <gotar at pld-linux.org>


From gotar at polanet.pl  Sat Nov  7 18:37:37 2009
From: gotar at polanet.pl (Tomasz Pala)
Date: Sat, 7 Nov 2009 18:37:37 +0100
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <alpine.LNX.2.00.0911071756420.17150@fgnss.gnfx.tqn.cy>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<packages_secpanel_TODO.NONE@pld-linux.org>
	<packages_secpanel_TODO.1.1@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
	<20091107155600.GB12086@sith.mimuw.edu.pl>
	<alpine.LNX.2.00.0911071756420.17150@fgnss.gnfx.tqn.cy>
Message-ID: <20091107173736.GB19608@polanet.pl>

On Sat, Nov 07, 2009 at 17:57:11 +0100, Pawel Golaszewski wrote:

> TODOs in spec is a mess...

And how do you call 1-line TODO in separate file?
One can easily forgot to update such file while fixing spec, assuming he
knows about it first. It also doesn't make connecting spec revision with
TODOs easier at all.

-- 
Tomasz Pala <gotar at pld-linux.org>


From gotar at polanet.pl  Sat Nov  7 18:44:45 2009
From: gotar at polanet.pl (Tomasz Pala)
Date: Sat, 7 Nov 2009 18:44:45 +0100
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <alpine.LNX.2.00.0911071743030.17150@fgnss.gnfx.tqn.cy>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<packages_secpanel_TODO.NONE@pld-linux.org>
	<packages_secpanel_TODO.1.1@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
	<alpine.LNX.2.00.0911071743030.17150@fgnss.gnfx.tqn.cy>
Message-ID: <20091107174445.GC19608@polanet.pl>

On Sat, Nov 07, 2009 at 17:47:48 +0100, Pawel Golaszewski wrote:

> You can put there a lot more info that in spec header, without any "^#". 

There isn't usually any more to write.

> Compilation errors, whatever.

Have never encoutered one.

> I never liked long TODO's in spec headers. It's only noise.

I never liked multiple %desc or subpackages. Just get used to it.

> It can be packaged as doc. Easy to do. Packaging it and putting as Source 
> will fix previous issue...

That would be really a mess. Consider conflicts with shipped TODO files.

-- 
Tomasz Pala <gotar at pld-linux.org>


From blues at pld-linux.org  Sat Nov  7 19:25:52 2009
From: blues at pld-linux.org (Pawel Golaszewski)
Date: Sat, 7 Nov 2009 19:25:52 +0100 (CET)
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <20091107174445.GC19608@polanet.pl>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<packages_secpanel_TODO.NONE@pld-linux.org>
	<packages_secpanel_TODO.1.1@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
	<alpine.LNX.2.00.0911071743030.17150@fgnss.gnfx.tqn.cy>
	<20091107174445.GC19608@polanet.pl>
Message-ID: <alpine.LNX.2.00.0911071908340.17150@fgnss.gnfx.tqn.cy>

On Sat, 7 Nov 2009, Tomasz Pala wrote:
> > Compilation errors, whatever.
> Have never encoutered one.

no?
Look at openoffice.org.spec. Good luck.
NOTE, TODO, MAYBE TODO,

> > I never liked long TODO's in spec headers. It's only noise.
> I never liked multiple %desc or subpackages. Just get used to it.

reductio ad absurdum

> > It can be packaged as doc. Easy to do. Packaging it and putting as 
> > Source will fix previous issue...
> That would be really a mess. Consider conflicts with shipped TODO files.

TODO-PLD, PLD-TODO, whatever...
Debian uses that and there is no problem.
Putting that TODO in package as doc can be guide for users what can change 
in future (split into subpackages, whatever)
  
I don't want to fight for that but it can be very useful.

-- 
pozdr.  Pawe? Go?aszewski          jid:blues<at>jabber<dot>gda<dot>pl
--------------------------------------------------------------------------
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby
Pro-Logic Surround Sound with Bass Boost and all the music is free.

From blues at pld-linux.org  Sun Nov  8 21:13:14 2009
From: blues at pld-linux.org (Pawel Golaszewski)
Date: Sun, 8 Nov 2009 21:13:14 +0100 (CET)
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <alpine.LNX.2.00.0911071908340.17150@fgnss.gnfx.tqn.cy>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<packages_secpanel_TODO.NONE@pld-linux.org>
	<packages_secpanel_TODO.1.1@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
	<alpine.LNX.2.00.0911071743030.17150@fgnss.gnfx.tqn.cy>
	<20091107174445.GC19608@polanet.pl>
	<alpine.LNX.2.00.0911071908340.17150@fgnss.gnfx.tqn.cy>
Message-ID: <alpine.LNX.2.00.0911082112030.8591@fgnss.gnfx.tqn.cy>

On Sat, 7 Nov 2009, Pawel Golaszewski wrote:
> > > It can be packaged as doc. Easy to do. Packaging it and putting as 
> > > Source will fix previous issue...
> > That would be really a mess. Consider conflicts with shipped TODO 
> > files.
> TODO-PLD, PLD-TODO, whatever...
> Debian uses that and there is no problem.
> Putting that TODO in package as doc can be guide for users what can change 
> in future (split into subpackages, whatever)

Please, look at lighttpd.
It's packaged now.

-- 
pozdr.  Pawe? Go?aszewski          jid:blues<at>jabber<dot>gda<dot>pl
--------------------------------------------------------------------------
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby
Pro-Logic Surround Sound with Bass Boost and all the music is free.

From glen at pld-linux.org  Mon Nov  9 09:37:58 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Mon, 9 Nov 2009 10:37:58 +0200
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <20091107155600.GB12086@sith.mimuw.edu.pl>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
	<20091107155600.GB12086@sith.mimuw.edu.pl>
Message-ID: <200911091037.58451.glen@pld-linux.org>

On Saturday 07 November 2009 17:56:00 Jan Rekorajski wrote:
> On Fri, 06 Nov 2009, Jakub Bogusz wrote:
> > On Thu, Oct 29, 2009 at 09:15:20AM +0100, blues wrote:
> > > Author: blues                        Date: Thu Oct 29 08:15:20 2009 GMT
> > > Module: packages                      Tag: HEAD
> > > ---- Log message:
> > > - TODO
> > >
> > > ---- Files affected:
> > > packages/secpanel:
> > >    secpanel.spec (1.31 -> 1.32) , TODO (NONE -> 1.1)  (NEW)
>
> [...]
>
> > I don't find such way useful:
> > - when I download package by builder, I don't have ANY idea, that there
> >   even is any TODO
> > - TODO is not available in .src.rpm
>
> I second that. Blues please stop making this mess.

i third that, and it will be even more mess, as i and some other devs do 
continue adding the todo in "old" fashion. resulting todo lists in two 
different formats.

<shameless plug>
ps: for easy block commenting/uncommenting install okas[1] and press meta+\ in 
vim. (us keyboard preferred).

[1] http://glen.alkohol.ee/okas/
</shameless plug>
-- 
glen


From glen at delfi.ee  Mon Nov  9 09:46:39 2009
From: glen at delfi.ee (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Mon, 9 Nov 2009 10:46:39 +0200
Subject: SVN: toys/rsget.pl/rsget.pl
In-Reply-To: <10957@svn.pld-linux.org>
References: <10957@svn.pld-linux.org>
Message-ID: <200911091046.40293.glen@delfi.ee>

On Friday 06 November 2009 15:10:23 pawelz wrote:
> Log:
> - require Cwd if and only if getcwd() is used (thx sparky)
>
...
> ===========================================================================
>=== --- toys/rsget.pl/rsget.pl	(original)
> +++ toys/rsget.pl/rsget.pl	Fri Nov  6 14:10:22 2009
> @@ -8,10 +8,9 @@
>  #
>  use strict;
>  use warnings;
> -use Cwd;
>  my $rev = qq$Id$;
>
> -our $install_path = getcwd();
> +our $install_path = do { require Cwd; Cwd::getcwd(); };
>  our $local_path = $install_path;


what do you mean? it's always imported in such code method:

$ strace -ff -efile perl -e 'our $install_path = do { require Cwd; Cwd::getcwd(); };' 2>&1|grep Cwd |grep -v NOENT
stat64("/usr/lib/perl5/5.10.1/i686-pld-linux-thread-multi/Cwd.pm", {st_mode=S_IFREG|0644, st_size=21167, ...}) = 0
open("/usr/lib/perl5/5.10.1/i686-pld-linux-thread-multi/Cwd.pm", O_RDONLY|O_LARGEFILE) = 6
stat64("/usr/lib/perl5/5.10.1/i686-pld-linux-thread-multi/auto/Cwd/Cwd.so", {st_mode=S_IFREG|0755, st_size=10864, ...}) = 0
open("/usr/lib/perl5/5.10.1/i686-pld-linux-thread-multi/auto/Cwd/Cwd.so", O_RDONLY) = 6

$ strace -ff -efile perl -e 'our $install_path = do { require Cwd; Cwd::getcwd(); }; print $install_path;' 2>&1|grep Cwd |grep -v NOENT
stat64("/usr/lib/perl5/5.10.1/i686-pld-linux-thread-multi/Cwd.pm", {st_mode=S_IFREG|0644, st_size=21167, ...}) = 0
open("/usr/lib/perl5/5.10.1/i686-pld-linux-thread-multi/Cwd.pm", O_RDONLY|O_LARGEFILE) = 6
stat64("/usr/lib/perl5/5.10.1/i686-pld-linux-thread-multi/auto/Cwd/Cwd.so", {st_mode=S_IFREG|0755, st_size=10864, ...}) = 0
open("/usr/lib/perl5/5.10.1/i686-pld-linux-thread-multi/auto/Cwd/Cwd.so", O_RDONLY) = 6


-- 
glen


From blues at pld-linux.org  Mon Nov  9 12:18:27 2009
From: blues at pld-linux.org (Pawel Golaszewski)
Date: Mon, 9 Nov 2009 12:18:27 +0100 (CET)
Subject: packages: secpanel/secpanel.spec, secpanel/TODO (NEW) - TODO
In-Reply-To: <200911091037.58451.glen@pld-linux.org>
References: <packages_secpanel_secpanel.spec.1.31@pld-linux.org>
	<20091106220822.GC26745@stranger.qboosh.pl>
	<20091107155600.GB12086@sith.mimuw.edu.pl>
	<200911091037.58451.glen@pld-linux.org>
Message-ID: <alpine.LNX.2.00.0911091218090.10332@fgnss.gnfx.tqn.cy>

On Mon, 9 Nov 2009, Elan Ruusam?e wrote:
> > > > Author: blues                        Date: Thu Oct 29 08:15:20 2009 GMT
> > > > Module: packages                      Tag: HEAD
> > > > ---- Log message:
> > > > - TODO
> > > >
> > > > ---- Files affected:
> > > > packages/secpanel:
> > > >    secpanel.spec (1.31 -> 1.32) , TODO (NONE -> 1.1)  (NEW)
> >
> > [...]
> >
> > > I don't find such way useful:
> > > - when I download package by builder, I don't have ANY idea, that there
> > >   even is any TODO
> > > - TODO is not available in .src.rpm
> > I second that. Blues please stop making this mess.
> i third that, and it will be even more mess, as i and some other devs do 
> continue adding the todo in "old" fashion. resulting todo lists in two 
> different formats.

ok, let it be.

-- 
pozdr.  Pawe? Go?aszewski          jid:blues<at>jabber<dot>gda<dot>pl
--------------------------------------------------------------------------
If you think of MS-DOS as mono, and Windows as stereo, then Linux is Dolby
Pro-Logic Surround Sound with Bass Boost and all the music is free.

From z at xatka.net  Tue Nov 10 12:16:29 2009
From: z at xatka.net (=?iso-8859-2?Q?Pawe=B3?= Zuzelski)
Date: Tue, 10 Nov 2009 12:16:29 +0100
Subject: packages: notification-daemon/notification-daemon.spec - O/P
	the dbus inter...
In-Reply-To: <packages_notification_daemon_notification_daemon.spec.1.27@pld-linux.org>
References: <packages_notification_daemon_notification_daemon.spec.1.26@pld-linux.org>
	<packages_notification_daemon_notification_daemon.spec.1.27@pld-linux.org>
Message-ID: <20091110111629.GB4368@davabel.touk.pl>

On Tue, 10 Nov 2009, patrys wrote:

> Author: patrys                       Date: Tue Nov 10 09:24:06 2009 GMT
> Module: packages                      Tag: HEAD
> ---- Log message:
> - O/P the dbus interface
> (...)
> +Obsoletes:	dbus(org.freedesktop.Notifications)

That is not true.

I use at least three programs that provides dbus(o.f.N) on the same
system, at the same time.

Why do you need this dependency?

-- 
Pozdrawiam,
Pawe? Zuzelski


From wrobell at pld-linux.org  Thu Nov 12 20:07:53 2009
From: wrobell at pld-linux.org (wrobell)
Date: Thu, 12 Nov 2009 19:07:53 +0000
Subject: packages: poppler/poppler.spec - explicitly disable gtk test
In-Reply-To: <packages_poppler_poppler.spec.1.90@pld-linux.org>
References: <packages_poppler_poppler.spec.1.89@pld-linux.org>
	<packages_poppler_poppler.spec.1.90@pld-linux.org>
Message-ID: <20091112190753.GI27664@borg.lan>

On Thu, Nov 12, 2009 at 11:36:48AM +0100, patrys wrote:
> Author: patrys                       Date: Thu Nov 12 10:36:48 2009 GMT
> Module: packages                      Tag: HEAD
> ---- Log message:
> - explicitly disable gtk test

why?

    wrobell <wrobell at pld-linux.org>


From patrys at pld-linux.org  Thu Nov 12 20:10:54 2009
From: patrys at pld-linux.org (Patryk Zawadzki)
Date: Thu, 12 Nov 2009 20:10:54 +0100
Subject: packages: poppler/poppler.spec - explicitly disable gtk test
In-Reply-To: <20091112190753.GI27664@borg.lan>
References: <packages_poppler_poppler.spec.1.89@pld-linux.org>
	<packages_poppler_poppler.spec.1.90@pld-linux.org>
	<20091112190753.GI27664@borg.lan>
Message-ID: <89b6ba3a0911121110v7a5079f0g788b5f56cd0c61d@mail.gmail.com>

On Thu, Nov 12, 2009 at 8:07 PM, wrobell <wrobell at pld-linux.org> wrote:
> On Thu, Nov 12, 2009 at 11:36:48AM +0100, patrys wrote:
>> Author: patrys ? ? ? ? ? ? ? ? ? ? ? Date: Thu Nov 12 10:36:48 2009 GMT
>> Module: packages ? ? ? ? ? ? ? ? ? ? ?Tag: HEAD
>> ---- Log message:
>> - explicitly disable gtk test
> why?

Because it does not result in any functionality and introduces a
dependency loop:

gtk+2 ? cairo ? poppler ? gtk+2

-- 
Patryk Zawadzki


From glen at pld-linux.org  Tue Nov 17 16:57:19 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Tue, 17 Nov 2009 17:57:19 +0200
Subject: packages: rpm-build-macros/rpm.macros - dont overwrite %__cmake,
	%__scons, ...
In-Reply-To: <packages_rpm_build_macros_rpm.macros.1.525@pld-linux.org>
References: <packages_rpm_build_macros_rpm.macros.1.524@pld-linux.org>
	<packages_rpm_build_macros_rpm.macros.1.525@pld-linux.org>
Message-ID: <200911171757.20123.glen@pld-linux.org>

On Tuesday 17 November 2009 17:51:58 sparky wrote:
> Author: sparky                       Date: Tue Nov 17 15:51:58 2009 GMT
> Module: packages                      Tag: HEAD
> ---- Log message:
> - dont overwrite %__cmake, %__scons, %__waf with versions without
> %{?_smp_mflags}
>
> ---- Files affected:
> packages/rpm-build-macros:
>    rpm.macros (1.524 -> 1.525)
>
> ---- Diffs:
>
> ================================================================
> Index: packages/rpm-build-macros/rpm.macros
> diff -u packages/rpm-build-macros/rpm.macros:1.524
> packages/rpm-build-macros/rpm.macros:1.525 ---
> packages/rpm-build-macros/rpm.macros:1.524	Fri Oct 16 07:41:34 2009 +++
> packages/rpm-build-macros/rpm.macros	Tue Nov 17 16:51:52 2009
> @@ -199,7 +199,6 @@
>  	%{dependencytracking} \
>  }
>
> -%__cmake	/usr/bin/cmake

???

now the macros are undefined!?

what's the purpose?

maybe you just redefine %{?_smp_mflags} in your local macros? (+ 
add %{?_smp_mflags} to %__cmake/...?)

and besides your local macros always overwrite system macros, not vice versa.

-- 
glen


From zbyniu at geocarbon.pl  Tue Nov 17 18:44:52 2009
From: zbyniu at geocarbon.pl (Zbyniu Krzystolik)
Date: Tue, 17 Nov 2009 18:44:52 +0100
Subject: packages: rpm-build-macros/rpm.macros - dont overwrite
	%__cmake, %__scons, ...
In-Reply-To: <200911171757.20123.glen@pld-linux.org>
References: <packages_rpm_build_macros_rpm.macros.1.524@pld-linux.org>
	<packages_rpm_build_macros_rpm.macros.1.525@pld-linux.org>
	<200911171757.20123.glen@pld-linux.org>
Message-ID: <20091117174452.GZ21820@geocarbon.pl>

Elan Ruusam?e wrote:
> > -%__cmake	/usr/bin/cmake
> 
> ???
> 
> now the macros are undefined!?

vim +31 rpm-build-macros/rpm.macros

> what's the purpose?

Parallel build via scons, cmake etc, as make do.

Zbyniu
-- 
%% Absolutely nothing we trust %%


From glen at pld-linux.org  Wed Nov 18 00:27:09 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Wed, 18 Nov 2009 01:27:09 +0200
Subject: packages: VirtualBox/VirtualBox.spec - --without userspace --with
	kernel fa...
In-Reply-To: <packages_VirtualBox_VirtualBox.spec.1.238@pld-linux.org>
References: <packages_VirtualBox_VirtualBox.spec.1.237@pld-linux.org>
	<packages_VirtualBox_VirtualBox.spec.1.238@pld-linux.org>
Message-ID: <200911180127.09318.glen@pld-linux.org>

On Wednesday 18 November 2009 00:44:01 adamg wrote:
> Author: adamg                        Date: Tue Nov 17 22:44:01 2009 GMT
> Module: packages                      Tag: HEAD
> ---- Log message:
> - --without userspace --with kernel fails due to missing mount.vboxsf,
>   move it from kernel subpackage to main package

is it packaging problem? or what "fails"?

if yes, then find workaround to fix it as it's totally pointless to install 
60mb of main package to guest just to get Shared Mounts working inside guest 
(the tiny mount.vboxsf binary is only need besides kernel modules).

extra subpackage for mount.vboxsf as alternative sounds silly too.

-- 
glen


From sparky at pld-linux.org  Wed Nov 18 04:32:03 2009
From: sparky at pld-linux.org (Przemyslaw Iskra)
Date: Wed, 18 Nov 2009 04:32:03 +0100
Subject: packages: VirtualBox/VirtualBox.spec - --without userspace
	--with kernel fa...
In-Reply-To: <200911180127.09318.glen@pld-linux.org>
References: <packages_VirtualBox_VirtualBox.spec.1.237@pld-linux.org>
	<packages_VirtualBox_VirtualBox.spec.1.238@pld-linux.org>
	<200911180127.09318.glen@pld-linux.org>
Message-ID: <20091118033203.GA27768@pld-linux.org>

On Wed, Nov 18, 2009 at 01:27:09AM +0200, Elan Ruusam?e wrote:
> On Wednesday 18 November 2009 00:44:01 adamg wrote:
> > Author: adamg                        Date: Tue Nov 17 22:44:01 2009 GMT
> > Module: packages                      Tag: HEAD
> > ---- Log message:
> > - --without userspace --with kernel fails due to missing mount.vboxsf,
> >   move it from kernel subpackage to main package
> 
> is it packaging problem? or what "fails"?

I beleve mount.vboxsf is built as part of userspace, so there will be no
file to package if only kernel modules are built.
 
> extra subpackage for mount.vboxsf as alternative sounds silly too.

why does it ? It probably is the only way anyways, think about multiple
kernel versions installed at once.

-- 
 ____  Sparky{PI] -- Przemyslaw _  ___  _  _  ........... LANG...Pl..Ca..Es..En
/____) ___  ___  _ _ || Iskra  |  | _ \| |  | : WWW........ppcrcd.pld-linux.org
\____\| -_)'___| ||^'||//\\// <   |  _/| |  | : JID......sparky<at>jabberes.org
(____/||   (_-_|_||  ||\\ ||   |_ |_|  |_| _| : Mail....sparky<at>pld-linux.org


From glen at pld-linux.org  Wed Nov 18 09:46:34 2009
From: glen at pld-linux.org (Elan =?utf-8?q?Ruusam=C3=A4e?=)
Date: Wed, 18 Nov 2009 10:46:34 +0200
Subject: packages: VirtualBox/VirtualBox.spec - --without userspace --with
	kernel fa...
In-Reply-To: <20091118033203.GA27768@pld-linux.org>
References: <packages_VirtualBox_VirtualBox.spec.1.237@pld-linux.org>
	<200911180127.09318.glen@pld-linux.org>
	<20091118033203.GA27768@pld-linux.org>
Message-ID: <200911181046.34973.glen@pld-linux.org>

On Wednesday 18 November 2009 05:32:03 Przemyslaw Iskra wrote:
> On Wed, Nov 18, 2009 at 01:27:09AM +0200, Elan Ruusam?e wrote:
> > On Wednesday 18 November 2009 00:44:01 adamg wrote:
> > > Author: adamg                        Date: Tue Nov 17 22:44:01 2009 GMT
> > > Module: packages                      Tag: HEAD
> > > ---- Log message:
> > > - --without userspace --with kernel fails due to missing mount.vboxsf,
> > >   move it from kernel subpackage to main package
> >
> > is it packaging problem? or what "fails"?
>
> I beleve mount.vboxsf is built as part of userspace, so there will be no
> file to package if only kernel modules are built.

it is very simple wrapper. maybe it should be included packaged by mount 
package?

so far i added linking of it in %{with kernel} part and problem solved for now

> > extra subpackage for mount.vboxsf as alternative sounds silly too.
>
> why does it ? It probably is the only way anyways, think about multiple
> kernel versions installed at once.

this will fail by some other dependencies, like vidia and if the binary 
checksum is identical rpm will allow installing the same file twice, at least 
in multilib case, not sure for same-arch-case how it behaves.

-- 
glen


From adamg at pld-linux.org  Wed Nov 18 10:07:27 2009
From: adamg at pld-linux.org (=?UTF-8?B?QWRhbSBHb8WCxJliaW93c2tp?=)
Date: Wed, 18 Nov 2009 10:07:27 +0100
Subject: packages: VirtualBox/VirtualBox.spec - --without userspace	--with
	kernel fa...
In-Reply-To: <20091118033203.GA27768@pld-linux.org>
References: <packages_VirtualBox_VirtualBox.spec.1.237@pld-linux.org>	<packages_VirtualBox_VirtualBox.spec.1.238@pld-linux.org>	<200911180127.09318.glen@pld-linux.org>
	<20091118033203.GA27768@pld-linux.org>
Message-ID: <4B03B94F.3090504@pld-linux.org>

W dniu 2009-11-18 04:32, Przemyslaw Iskra pisze:
> why does it ? It probably is the only way anyways, think about multiple
> kernel versions installed at once.

Honestly I didn't think of that, but in that case to avoid file 
conflicts when multiple kernel*-misc-vbox* packages are installed we 
should also probably move init scripts as well.

-- 
  http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
    PLD Linux developer    | Everybody needs some solid rock, I know I do.


From hawk at limanowa.net  Wed Nov 18 14:51:21 2009
From: hawk at limanowa.net (Marcin Krol)
Date: Wed, 18 Nov 2009 14:51:21 +0100
Subject: packages: VirtualBox/VirtualBox.spec - --without userspace --with
	kernel fa...
In-Reply-To: <200911181046.34973.glen@pld-linux.org>
References: <packages_VirtualBox_VirtualBox.spec.1.237@pld-linux.org>	<200911180127.09318.glen@pld-linux.org>	<20091118033203.GA27768@pld-linux.org>
	<200911181046.34973.glen@pld-linux.org>
Message-ID: <4B03FBD9.9010100@limanowa.net>

> this will fail by some other dependencies, like vidia and if the binary 
> checksum is identical rpm will allow installing the same file twice, at least 
> in multilib case, not sure for same-arch-case how it behaves.

I have multiple kernel*-misc-vbox* on same arch and there were no
conflicts on install.

M.


From sparky at pld-linux.org  Wed Nov 18 17:07:00 2009
From: sparky at pld-linux.org (Przemyslaw Iskra)
Date: Wed, 18 Nov 2009 17:07:00 +0100
Subject: RFC: Convert bconds to autoconf-like options.
Message-ID: <20091118160700.GA415@pld-linux.org>


Because I don't expect any constructive feedback just yet I'm going to
introduce the changes right away and we will discuss and later fix them
eventually.


I'm proposing few macros to easily convert bconds to configure options.
Implementation looks like this:


# expand bconds to --enable-something and --disable-something
%__enable() %{expand:%%{?with_%{1}:--enable-%{?2}%{!?2:%{1}}}}
%__disable() %{expand:%%{!?with_%{1}:--disable-%{?2}%{!?2:%{1}}}}
%__enable_disable() --%{expand:%%{?with_%{1}:en}%%{!?with_%{1}:dis}}able-%{?2}%{!?2:%{1}}

# same as above, but condition inverted
%__enable_unless() %{expand:%%{!?with_%{1}:--enable-%{?2}%{!?2:%{1}}}}
%__disable_if() %{expand:%%{?with_%{1}:--disable-%{?2}%{!?2:%{1}}}}
%__enable_disable_not() --%{expand:%%{!?with_%{1}:en}%%{?with_%{1}:dis}}able-%{?2}%{!?2:%{1}}

# expand bconds to --with-something and --without-something
%__with() %{expand:%%{?with_%{1}:--with-%{?2}%{!?2:%{1}}%{?3:=%{3}}}}
%__without() %{expand:%%{!?with_%{1}:--without-%{?2}%{!?2:%{1}}}}
%__with_without() %{expand:%%{?with_%{1}:--with-%{?2}%{!?2:%{1}}%{?3:=%{3}}}%%{!?with_%{1}:--without-%{?2}%{!?2:%{1}}}}

# same as above, but condition inverted
%__with_unless() %{expand:%%{!?with_%{1}:--with-%{?2}%{!?2:%{1}}%{?3:=%{3}}}}
%__without_if() %{expand:%%{?with_%{1}:--without-%{?2}%{!?2:%{1}}}}
%__with_without_not() %{expand:%%{!?with_%{1}:--with-%{?2}%{!?2:%{1}}%{?3:=%{3}}}%%{?with_%{1}:--without-%{?2}%{!?2:%{1}}}}



Each macro requires bcond name and accepts optional option name, if option
isn't specified bcond name is used as option name. Options returning
--with-something also allow third argument which will be added as value
in case or positive condition, but won't be added otherwise.

I was thinking using another prefix, but __ best mimics the two dashes in
front of options.

Examples:
* Basic enable and disable options: 
- %{__enable bcond}
   returns --enable-bcond if build condition "bcond" is set,
   returns nothing otherwise
- %{__enable bcond option}
   returns --enable-option if build condition "bcond" is set,
   returns nothing otherwise
- %{__disable bcond}
   returns --disable-bcond if build condition "bcond" is not set,
   returns nothing otherwise
- %{__enable_disable bcond}
   returns --enable-bcond if build condition "bcond" is set,
   returns --disable-bcond if build condition "bcond" is not set

* Negated enable and disable options, probably useful only with second argument:
- %{__enable_unless bcond option}
   returns --enable-option if build condition "bcond" is not set,
   returns nothing otherwise
- %{__disable_if bcond option}
   returns --disable-option if build condition "bcond" is set,
   returns nothing otherwise
- %{__enable_disable_not bcond option}
   returns --enable-option if build condition "bcond" is not set,
   returns --disable-option if build condition "bcond" is set

* Basic with and without options: 
- %{__with bcond}
   returns --with-bcond if build condition "bcond" is set,
   returns nothing otherwise
- %{__with bcond option}
   returns --with-option if build condition "bcond" is set,
   returns nothing otherwise
- %{__with bcond option value}
   returns --with-option=value if build condition "bcond" is set,
   returns nothing otherwise
- %{__without bcond}
   returns --without-bcond if build condition "bcond" is not set,
   returns nothing otherwise
- %{__with_without bcond}
   returns --with-bcond if build condition "bcond" is set,
   returns --without-bcond if build condition "bcond" is not set
- %{__with_without bcond option value}
   returns --with-option=value if build condition "bcond" is set,
   returns --without-option if build condition "bcond" is not set

* Negated with and without options, probably useful only with second argument:
- %{__with_unless bcond option}
   returns --with-option if build condition "bcond" is not set,
   returns nothing otherwise
- %{__with_unless bcond option value}
   returns --with-option=value if build condition "bcond" is not set,
   returns nothing otherwise
- %{__without_if bcond option}
   returns --without-option if build condition "bcond" is set,
   returns nothing otherwise
- %{__with_without_not bcond option}
   returns --with-option if build condition "bcond" is not set,
   returns --without-option if build condition "bcond" is set
- %{__with_without_not bcond option value}
   returns --with-option=value if build condition "bcond" is not set,
   returns --without-option if build condition "bcond" is set


That's how most options would be replaced, taken from mplayer:

-	%{?with_joystick:--enable-joystick} \
+	%{__enable joystick} \

-	%{!?with_ssse3:--disable-ssse3} \
+	%{__disable ssse3} \

-	--%{!?with_dvdnav:dis}%{?with_dvdnav:en}able-dvdnav \
+	%{__enable_disable dvdnav} \

-	%{!?with_amr:--disable-libopencore_amrnb --disable-libopencore_amrwb} \
-	%{?with_amr:--enable-libopencore_amrnb --enable-libopencore_amrwb} \
+	%{__enable_disable amr libopencore_amrnb} \
+	%{__enable_disable amr libopencore_amrwb} \

-	--%{?with_runtime:en}%{!?with_runtime:dis}able-runtime-cpudetection \
+	%{__enable_disable runtime runtime-cpudetection} \

Negated options are rather hard to understand so I'm not sure wether to add
them at all. In case below I think the old way is better:

- 	%{?with_alsa:--enable-alsa --disable-select} \
+	%{__enable alsa} %{__disable_if alsa select} \

If there are multiple options it probably is best to leave it as is:
 	%{?with_xmms:--enable-xmms --with-xmmsplugindir=%{_libdir}/xmms/Input --with-xmmslibdir=%{_libdir}}

because it would look like this:
	%{__enable xmms} \
	%{__with xmms xmmsplugindir %{_libdir}/xmms/Input} \
	%{__with xmms xmmslibindir %{_libdir}} \


Questions, comments anyone ?

-- 
 ____  Sparky{PI] -- Przemyslaw _  ___  _  _  ........... LANG...Pl..Ca..Es..En
/____) ___  ___  _ _ || Iskra  |  | _ \| |  | : WWW........ppcrcd.pld-linux.org
\____\| -_)'___| ||^'||//\\// <   |  _/| |  | : JID......sparky<at>jabberes.org
(____/||   (_-_|_||  ||\\ ||   |_ |_|  |_| _| : Mail....sparky<at>pld-linux.org


From n3npq at mac.com  Wed Nov 18 17:20:05 2009
From: n3npq at mac.com (Jeff Johnson)
Date: Wed, 18 Nov 2009 11:20:05 -0500
Subject: RFC: Convert bconds to autoconf-like options.
In-Reply-To: <20091118160700.GA415@pld-linux.org>
References: <20091118160700.GA415@pld-linux.org>
Message-ID: <75A586DC-FA85-431E-8BE2-C9AEE0D86423@mac.com>

Before you get into a litter of additional macros for
bconds, please note that when originally implemented
(by PLD, always first ;-) bcond's were intended as booleans.

When bconds were picked up by RPM using --with/--without popt aliases
(that are essentially just --define wrappings to conventionally
set macro strings), there was already an attempt to try to
conventionalize the string values to be passed straight to
./configure.

So there is a previous attempt to do what you seem to be attempting now.

Whether the existing mapping is flexible enough (or not) is an entirely
different issue than attempting a common conventional approach to
setting build options through RPM.

Personally, I don't believe the existing macro infrastructure in RPM
is robust enough to support full blown "build option" configuiration.

What should be done instead is to add additional macro primitives,
with a reliably defined "registry", not yet more gunky and obscure lazy
string expansions using the existing RPM macro implementation.

I can help with implementing macro primitives (and adding a "registry")
if you wish. YAML would likely be a representation markup that
isn't too painful, other approaches, using embedded lua symbol
tables instead of the existing macro store (which is quite feeble imho).

But you can do whatever you please too ...

73 de Jeff

On Nov 18, 2009, at 11:07 AM, Przemyslaw Iskra wrote:

> 
> Because I don't expect any constructive feedback just yet I'm going to
> introduce the changes right away and we will discuss and later fix them
> eventually.
> 
> 
> I'm proposing few macros to easily convert bconds to configure options.
> Implementation looks like this:
> 
> 
> # expand bconds to --enable-something and --disable-something
> %__enable() %{expand:%%{?with_%{1}:--enable-%{?2}%{!?2:%{1}}}}
> %__disable() %{expand:%%{!?with_%{1}:--disable-%{?2}%{!?2:%{1}}}}
> %__enable_disable() --%{expand:%%{?with_%{1}:en}%%{!?with_%{1}:dis}}able-%{?2}%{!?2:%{1}}
> 
> # same as above, but condition inverted
> %__enable_unless() %{expand:%%{!?with_%{1}:--enable-%{?2}%{!?2:%{1}}}}
> %__disable_if() %{expand:%%{?with_%{1}:--disable-%{?2}%{!?2:%{1}}}}
> %__enable_disable_not() --%{expand:%%{!?with_%{1}:en}%%{?with_%{1}:dis}}able-%{?2}%{!?2:%{1}}
> 
> # expand bconds to --with-something and --without-something
> %__with() %{expand:%%{?with_%{1}:--with-%{?2}%{!?2:%{1}}%{?3:=%{3}}}}
> %__without() %{expand:%%{!?with_%{1}:--without-%{?2}%{!?2:%{1}}}}
> %__with_without() %{expand:%%{?with_%{1}:--with-%{?2}%{!?2:%{1}}%{?3:=%{3}}}%%{!?with_%{1}:--without-%{?2}%{!?2:%{1}}}}
> 
> # same as above, but condition inverted
> %__with_unless() %{expand:%%{!?with_%{1}:--with-%{?2}%{!?2:%{1}}%{?3:=%{3}}}}
> %__without_if() %{expand:%%{?with_%{1}:--without-%{?2}%{!?2:%{1}}}}
> %__with_without_not() %{expand:%%{!?with_%{1}:--with-%{?2}%{!?2:%{1}}%{?3:=%{3}}}%%{?with_%{1}:--without-%{?2}%{!?2:%{1}}}}
> 
> 
> 
> Each macro requires bcond name and accepts optional option name, if option
> isn't specified bcond name is used as option name. Options returning
> --with-something also allow third argument which will be added as value
> in case or positive condition, but won't be added otherwise.
> 
> I was thinking using another prefix, but __ best mimics the two dashes in
> front of options.
> 
> Examples:
> * Basic enable and disable options: 
> - %{__enable bcond}
>   returns --enable-bcond if build condition "bcond" is set,
>   returns nothing otherwise
> - %{__enable bcond option}
>   returns --enable-option if build condition "bcond" is set,
>   returns nothing otherwise
> - %{__disable bcond}
>   returns --disable-bcond if build condition "bcond" is not set,
>   returns nothing otherwise
> - %{__enable_disable bcond}
>   returns --enable-bcond if build condition "bcond" is set,
>   returns --disable-bcond if build condition "bcond" is not set
> 
> * Negated enable and disable options, probably useful only with second argument:
> - %{__enable_unless bcond option}
>   returns --enable-option if build condition "bcond" is not set,
>   returns nothing otherwise
> - %{__disable_if bcond option}
>   returns --disable-option if build condition "bcond" is set,
>   returns nothing otherwise
> - %{__enable_disable_not bcond option}
>   returns --enable-option if build condition "bcond" is not set,
>   returns --disable-option if build condition "bcond" is set
> 
> * Basic with and without options: 
> - %{__with bcond}
>   returns --with-bcond if build condition "bcond" is set,
>   returns nothing otherwise
> - %{__with bcond option}
>   returns --with-option if build condition "bcond" is set,
>   returns nothing otherwise
> - %{__with bcond option value}
>   returns --with-option=value if build condition "bcond" is set,
>   returns nothing otherwise
> - %{__without bcond}
>   returns --without-bcond if build condition "bcond" is not set,
>   returns nothing otherwise
> - %{__with_without bcond}
>   returns --with-bcond if build condition "bcond" is set,
>   returns --without-bcond if build condition "bcond" is not set
> - %{__with_without bcond option value}
>   returns --with-option=value if build condition "bcond" is set,
>   returns --without-option if build condition "bcond" is not set
> 
> * Negated with and without options, probably useful only with second argument:
> - %{__with_unless bcond option}
>   returns --with-option if build condition "bcond" is not set,
>   returns nothing otherwise
> - %{__with_unless bcond option value}
>   returns --with-option=value if build condition "bcond" is not set,
>   returns nothing otherwise
> - %{__without_if bcond option}
>   returns --without-option if build condition "bcond" is set,
>   returns nothing otherwise
> - %{__with_without_not bcond option}
>   returns --with-option if build condition "bcond" is not set,
>   returns --without-option if build condition "bcond" is set
> - %{__with_without_not bcond option value}
>   returns --with-option=value if build condition "bcond" is not set,
>   returns --without-option if build condition "bcond" is set
> 
> 
> That's how most options would be replaced, taken from mplayer:
> 
> -	%{?with_joystick:--enable-joystick} \
> +	%{__enable joystick} \
> 
> -	%{!?with_ssse3:--disable-ssse3} \
> +	%{__disable ssse3} \
> 
> -	--%{!?with_dvdnav:dis}%{?with_dvdnav:en}able-dvdnav \
> +	%{__enable_disable dvdnav} \
> 
> -	%{!?with_amr:--disable-libopencore_amrnb --disable-libopencore_amrwb} \
> -	%{?with_amr:--enable-libopencore_amrnb --enable-libopencore_amrwb} \
> +	%{__enable_disable amr libopencore_amrnb} \
> +	%{__enable_disable amr libopencore_amrwb} \
> 
> -	--%{?with_runtime:en}%{!?with_runtime:dis}able-runtime-cpudetection \
> +	%{__enable_disable runtime runtime-cpudetection} \
> 
> Negated options are rather hard to understand so I'm not sure wether to add
> them at all. In case below I think the old way is better:
> 
> - 	%{?with_alsa:--enable-alsa --disable-select} \
> +	%{__enable alsa} %{__disable_if alsa select} \
> 
> If there are multiple options it probably is best to leave it as is:
> 	%{?with_xmms:--enable-xmms --with-xmmsplugindir=%{_libdir}/xmms/Input --with-xmmslibdir=%{_libdir}}
> 
> because it would look like this:
> 	%{__enable xmms} \
> 	%{__with xmms xmmsplugindir %{_libdir}/xmms/Input} \
> 	%{__with xmms xmmslibindir %{_libdir}} \
> 
> 
> Questions, comments anyone ?
> 
> -- 
> ____  Sparky{PI] -- Przemyslaw _  ___  _  _  ........... LANG...Pl..Ca..Es..En
> /____) ___  ___  _ _ || Iskra  |  | _ \| |  | : WWW........ppcrcd.pld-linux.org
> \____\| -_)'___| ||^'||//\\// <   |  _/| |  | : JID......sparky<at>jabberes.org
> (____/||   (_-_|_||  ||\\ ||   |_ |_|  |_| _| : Mail....sparky<at>pld-linux.org
> _______________________________________________
> pld-devel-en mailing list
> pld-devel-en at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3370 bytes
Desc: not available
URL: </mailman/pipermail/pld-devel-en/attachments/20091118/69758c09/attachment.p7s>

From sparky at pld-linux.org  Wed Nov 18 17:49:37 2009
From: sparky at pld-linux.org (Przemyslaw Iskra)
Date: Wed, 18 Nov 2009 17:49:37 +0100
Subject: RFC: Convert bconds to autoconf-like options.
In-Reply-To: <75A586DC-FA85-431E-8BE2-C9AEE0D86423@mac.com>
References: <20091118160700.GA415@pld-linux.org>
	<75A586DC-FA85-431E-8BE2-C9AEE0D86423@mac.com>
Message-ID: <20091118164937.GA5615@pld-linux.org>

On Wed, Nov 18, 2009 at 11:20:05AM -0500, Jeff Johnson wrote:
> Before you get into a litter of additional macros for
> bconds, please note that when originally implemented
> (by PLD, always first ;-) bcond's were intended as booleans.
> 
> When bconds were picked up by RPM using --with/--without popt aliases
> (that are essentially just --define wrappings to conventionally
> set macro strings), there was already an attempt to try to
> conventionalize the string values to be passed straight to
> ./configure.
> 
> So there is a previous attempt to do what you seem to be attempting now.
> 
> Whether the existing mapping is flexible enough (or not) is an entirely
> different issue than attempting a common conventional approach to
> setting build options through RPM.
> 
> Personally, I don't believe the existing macro infrastructure in RPM
> is robust enough to support full blown "build option" configuiration.
> 
> What should be done instead is to add additional macro primitives,
> with a reliably defined "registry", not yet more gunky and obscure lazy
> string expansions using the existing RPM macro implementation.
> 
> I can help with implementing macro primitives (and adding a "registry")
> if you wish. YAML would likely be a representation markup that
> isn't too painful, other approaches, using embedded lua symbol
> tables instead of the existing macro store (which is quite feeble imho).
> 
> But you can do whatever you please too ...

I only really care about %__enable_disable macro which replaces such
obscure PLD idiom:
	--%{?with_runtime:en}%{!?with_runtime:dis}able-runtime-cpudetection
with much more readable:
	%{__enable_disable runtime runtime-cpudetection}

All the other macros are to complete the implementation.


Your "registry" idea sounds very interesting, but PLD doesn't even have
standarized bcond names (not often, but they differ between spec files
sometimes). So implementing it would require a lot of effort from us.


-- 
 ____  Sparky{PI] -- Przemyslaw _  ___  _  _  ........... LANG...Pl..Ca..Es..En
/____) ___  ___  _ _ || Iskra  |  | _ \| |  | : WWW........ppcrcd.pld-linux.org
\____\| -_)'___| ||^'||//\\// <   |  _/| |  | : JID......sparky<at>jabberes.org
(____/||   (_-_|_||  ||\\ ||   |_ |_|  |_| _| : Mail....sparky<at>pld-linux.org


From n3npq at mac.com  Wed Nov 18 17:58:03 2009
From: n3npq at mac.com (Jeff Johnson)
Date: Wed, 18 Nov 2009 11:58:03 -0500
Subject: RFC: Convert bconds to autoconf-like options.
In-Reply-To: <20091118164937.GA5615@pld-linux.org>
References: <20091118160700.GA415@pld-linux.org>
	<75A586DC-FA85-431E-8BE2-C9AEE0D86423@mac.com>
	<20091118164937.GA5615@pld-linux.org>
Message-ID: <9013EE6D-C4B3-4E17-9655-CAEDA3A254A3@mac.com>


On Nov 18, 2009, at 11:49 AM, Przemyslaw Iskra wrote:
> 
> I only really care about %__enable_disable macro which replaces such
> obscure PLD idiom:
> 	--%{?with_runtime:en}%{!?with_runtime:dis}able-runtime-cpudetection
> with much more readable:
> 	%{__enable_disable runtime runtime-cpudetection}
> 

Certainly macros are eye scratching pugliness, you will get no argument
from me.

> All the other macros are to complete the implementation.
> 
> 
> Your "registry" idea sounds very interesting, but PLD doesn't even have
> standarized bcond names (not often, but they differ between spec files
> sometimes). So implementing it would require a lot of effort from us.
> 

If there's some fundamental design, particularly with naming conventions
(hint: just steal AutoFu conventions and put a _ in front of the names),
then a "registry" and inheiritance and YAML/XML/JSON/WHATEVER markup
and more could (and should) be attempted. Without strong design
conventions, well, PLD has strong methodology even if most distros
don't wrto RPM macros.

But certainly RPM macro eye scratchiness can always be attempted
by adding Yet Another Layer of abstraction.

At some point its quite hard to tell how a build should be done ...


73 de Jeff
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3370 bytes
Desc: not available
URL: </mailman/pipermail/pld-devel-en/attachments/20091118/dcf7c82c/attachment.p7s>

From glen at pld-linux.org  Wed Nov 18 19:08:57 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Wed, 18 Nov 2009 20:08:57 +0200
Subject: RFC: Convert bconds to autoconf-like options.
In-Reply-To: <20091118164937.GA5615@pld-linux.org>
References: <20091118160700.GA415@pld-linux.org>
	<75A586DC-FA85-431E-8BE2-C9AEE0D86423@mac.com>
	<20091118164937.GA5615@pld-linux.org>
Message-ID: <200911182008.57643.glen@pld-linux.org>

On Wednesday 18 November 2009 18:49:37 Przemyslaw Iskra wrote:
> Your "registry" idea sounds very interesting, but PLD doesn't even have
> standarized bcond names (not often, but they differ between spec files
> sometimes). So implementing it would require a lot of effort from us.

which reminded that i kind of collected the bconds usage and commited to cvs 
it some time ago (restored from old cvs path and refreshed now):

http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/packages/bconds.txt

-- 
glen


From glen at pld-linux.org  Wed Nov 18 19:15:40 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Wed, 18 Nov 2009 20:15:40 +0200
Subject: flat SPECS available!
In-Reply-To: <200904291255.40657.mmazur@kernel.pl>
References: <200904271815.49920.arekm@maven.pl>
	<200904291255.40657.mmazur@kernel.pl>
Message-ID: <200911182015.40619.glen@pld-linux.org>

On Wednesday 29 April 2009 13:55:40 Mariusz Mazur wrote:
> I just did a server-side read-only SPECS that's full of symlinks to
> the ../packages spec files. I've also added a small monitoring script that
> will rename/delete/create new symlinks whenever a directory in packages/
> gets created/deleted/renamed.


if you care, then it has "lost" few specs:

$ cvs up
cvs server: Updating .
cvs server: nothing known about ario.spec
cvs server: nothing known about fonts-TTF-CRULP-Nafees_Tahrer_Naskh.spec
cvs server: nothing known about freeipa.spec
cvs server: nothing known about nekovm.spec
cvs server: nothing known about pdfmod.spec
cvs server: nothing known about perl-Declare-Constraints-Simple-Library.spec
cvs server: nothing known about php-backup-arekm.spec
cvs server: nothing known about psyced.spec
cvs server: nothing known about rpmrebuild.spec

these are dead symlinks on server side, and somebody doing `cvs add' for a 
dir, but never commiting a spec?

# grep freeip /var/log/flatspecsd
Thu May 28 10:26:26 CEST 2009 CREATE freeipa

# TZ=CET la ../packages/freeipa
total 556
drwxrwxr-x     2 cvs cvs      6 2009-05-28 10:26 ./
drwxrwxr-x 14348 cvs cvs 389120 2009-11-18 19:07 ../


> Enjoy.
>
> --mmazur


-- 
glen


From sparky at pld-linux.org  Wed Nov 18 19:31:18 2009
From: sparky at pld-linux.org (Przemyslaw Iskra)
Date: Wed, 18 Nov 2009 19:31:18 +0100
Subject: flat SPECS available!
In-Reply-To: <200911182015.40619.glen@pld-linux.org>
References: <200904271815.49920.arekm@maven.pl>
	<200904291255.40657.mmazur@kernel.pl>
	<200911182015.40619.glen@pld-linux.org>
Message-ID: <20091118183118.GA3426@pld-linux.org>

On Wed, Nov 18, 2009 at 08:15:40PM +0200, Elan Ruusam?e wrote:
> On Wednesday 29 April 2009 13:55:40 Mariusz Mazur wrote:
> > I just did a server-side read-only SPECS that's full of symlinks to
> > the ../packages spec files. I've also added a small monitoring script that
> > will rename/delete/create new symlinks whenever a directory in packages/
> > gets created/deleted/renamed.
> 
> 
> if you care, then it has "lost" few specs:
> 
> $ cvs up
> cvs server: Updating .
> cvs server: nothing known about ario.spec
> cvs server: nothing known about fonts-TTF-CRULP-Nafees_Tahrer_Naskh.spec
> cvs server: nothing known about freeipa.spec
> cvs server: nothing known about nekovm.spec
> cvs server: nothing known about pdfmod.spec
> cvs server: nothing known about perl-Declare-Constraints-Simple-Library.spec
> cvs server: nothing known about php-backup-arekm.spec
> cvs server: nothing known about psyced.spec
> cvs server: nothing known about rpmrebuild.spec
> 
> these are dead symlinks on server side, and somebody doing `cvs add' for a 
> dir, but never commiting a spec?

On another matter, is there a way to actually delete a directory ?
(other than asking cvsadmin)

I think the script should track DIR/DIR.spec,v files only.

-- 
 ____  Sparky{PI] -- Przemyslaw _  ___  _  _  ........... LANG...Pl..Ca..Es..En
/____) ___  ___  _ _ || Iskra  |  | _ \| |  | : WWW........ppcrcd.pld-linux.org
\____\| -_)'___| ||^'||//\\// <   |  _/| |  | : JID......sparky<at>jabberes.org
(____/||   (_-_|_||  ||\\ ||   |_ |_|  |_| _| : Mail....sparky<at>pld-linux.org


From sparky at pld-linux.org  Thu Nov 19 22:59:41 2009
From: sparky at pld-linux.org (Przemyslaw Iskra)
Date: Thu, 19 Nov 2009 22:59:41 +0100
Subject: packages: libx264/libx264.spec - just call this version 1.1.3
In-Reply-To: <packages_libx264_libx264.spec.1.25@pld-linux.org>
References: <packages_libx264_libx264.spec.1.24@pld-linux.org>
	<packages_libx264_libx264.spec.1.25@pld-linux.org>
Message-ID: <20091119215941.GA14314@pld-linux.org>

On Thu, Nov 19, 2009 at 10:35:52PM +0100, arekm wrote:
> Author: arekm                        Date: Thu Nov 19 21:35:52 2009 GMT
> Module: packages                      Tag: HEAD
> ---- Log message:
> - just call this version 1.1.3

>  Name:		libx264
> -Version:	0.1.2
> +Version:	0.1.3
>  Release:	1.%{snap}_%{snaph}.%{rel}

I would call it 79, same as so version, because it is the only version
they refer to:
Version: 79

And drop shapshot hour from release:
Release: 0.%{snap}.%{rel}

-- 
 ____  Sparky{PI] -- Przemyslaw _  ___  _  _  ........... LANG...Pl..Ca..Es..En
/____) ___  ___  _ _ || Iskra  |  | _ \| |  | : WWW........ppcrcd.pld-linux.org
\____\| -_)'___| ||^'||//\\// <   |  _/| |  | : JID......sparky<at>jabberes.org
(____/||   (_-_|_||  ||\\ ||   |_ |_|  |_| _| : Mail....sparky<at>pld-linux.org


From sparky at pld-linux.org  Fri Nov 20 21:09:20 2009
From: sparky at pld-linux.org (Przemyslaw Iskra)
Date: Fri, 20 Nov 2009 21:09:20 +0100
Subject: mplayer and gnome-screensaver
In-Reply-To: <packages_mplayer_mplayer.spec.1.433@pld-linux.org>
References: <packages_mplayer_mplayer.spec.1.432@pld-linux.org>
	<packages_mplayer_mplayer.spec.1.433@pld-linux.org>
Message-ID: <20091120200920.GA28981@pld-linux.org>

On Fri, Nov 20, 2009 at 07:47:36PM +0100, sparky wrote:

> +# update, hard to fix right now because of gnome bug 579430:
> +# https://bugzilla.gnome.org/show_bug.cgi?id=579430
>  #Patch32:	%{name}-gnome-screensaver.patch

I was thinking about writing new patch based on code from
gnome-screensaver-command, which would send "SimulateUserActivity" every
30 seconds. But there is a problem with it, gnome-screensaver gets stuck
in "inhibit" mode and won't activate again.

try to execute:
$ gnome-screensaver-command --poke
and check whether or not the screensaver activates after specified time
of inactivity.

Does anyone know how "inhibit" message is supposed to work ? Because I'm
quite sure it isn't what gnome-screensaver-command --inhibit does.

-- 
 ____  Sparky{PI] -- Przemyslaw _  ___  _  _  ........... LANG...Pl..Ca..Es..En
/____) ___  ___  _ _ || Iskra  |  | _ \| |  | : WWW........ppcrcd.pld-linux.org
\____\| -_)'___| ||^'||//\\// <   |  _/| |  | : JID......sparky<at>jabberes.org
(____/||   (_-_|_||  ||\\ ||   |_ |_|  |_| _| : Mail....sparky<at>pld-linux.org


From glen at pld-linux.org  Wed Nov 18 21:44:03 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Wed, 18 Nov 2009 22:44:03 +0200
Subject: R: kernel pkg
Message-ID: <200911182244.03209.glen@pld-linux.org>

hi

remind me why we do not setup R: kernel-package in userspace packages and not even vice versa?

i'm so tempted to add to VirtualBox.spec:
%{?with_dist_kernel:Requires:    kernel%{_alt_kernel}-misc-vboxdrv = %{rel}@%{_kernel_ver_str}}

or at least:
%{?with_dist_kernel:Suggesgts:    kernel%{_alt_kernel}-misc-vboxdrv}

-- 
glen


From arekm at maven.pl  Sun Nov 22 11:45:58 2009
From: arekm at maven.pl (Arkadiusz Miskiewicz)
Date: Sun, 22 Nov 2009 11:45:58 +0100
Subject: R: kernel pkg
In-Reply-To: <200911182244.03209.glen@pld-linux.org>
References: <200911182244.03209.glen@pld-linux.org>
Message-ID: <200911221145.58195.arekm@maven.pl>

On Wednesday 18 of November 2009, Elan Ruusam?e wrote:
> hi
> 
> remind me why we do not setup R: kernel-package in userspace packages and
>  not even vice versa?

Because some of us use non packaged kernels.

Suggests would be better.
-- 
Arkadiusz Mi?kiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/


From kiesiu at kiesiu.com  Sun Nov 22 17:47:10 2009
From: kiesiu at kiesiu.com (Lukasz Kies)
Date: Sun, 22 Nov 2009 17:47:10 +0100
Subject: rc-scripts-0.4.2.6-2 breaks localtime hwclock sync
Message-ID: <1adc5bd30911220847x4721314aqfe0e72594dd14a6a@mail.gmail.com>

Dear All,

rc-scripts-0.4.2.6-2 from Th test breaks localtime hwclock synchronization.
In this version someone changed options for hwclock in case of
localtime clock from --localtime to -l and in case of UTC clock from
--utc to -u.
The UTC change is correct but hwclock doesn't regonize -l option.

[kiesiu at beth ~]$ rpm -q rc-scripts util-linux-ng
rc-scripts-0.4.2.6-2.i686
util-linux-ng-2.16.1-1.i686

Please revert this change. Patch for rc.sysinit in attachment. Thank you.

Regards,
Lukasz Kies
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rc.sysinit.patch
Type: application/octet-stream
Size: 301 bytes
Desc: not available
URL: </mailman/pipermail/pld-devel-en/attachments/20091122/eda64d7c/attachment.obj>

From ankry at green.mif.pg.gda.pl  Sun Nov 22 18:36:34 2009
From: ankry at green.mif.pg.gda.pl (Andrzej Krzysztofowicz)
Date: Sun, 22 Nov 2009 18:36:34 +0100 (CET)
Subject: R: kernel pkg
In-Reply-To: <200911221145.58195.arekm@maven.pl>
Message-ID: <200911221736.nAMHaY12020449@green.mif.pg.gda.pl>

Arkadiusz Miskiewicz wrote:
> 
> On Wednesday 18 of November 2009, Elan Ruusam??e wrote:
> > hi
> > 
> > remind me why we do not setup R: kernel-package in userspace packages and
> >  not even vice versa?
> 
> Because some of us use non packaged kernels.

And because kernel may be external to some environments?
Eg. xen, chroot.

> Suggests would be better.

-- 
=======================================================================
  Andrzej M. Krzysztofowicz                  ankry at mif.pg.gda.pl


From kiesiu at kiesiu.com  Sun Nov 22 22:14:32 2009
From: kiesiu at kiesiu.com (Lukasz Kies)
Date: Sun, 22 Nov 2009 22:14:32 +0100
Subject: rc-scripts-0.4.2.6-2 breaks localtime hwclock sync
In-Reply-To: <1adc5bd30911220847x4721314aqfe0e72594dd14a6a@mail.gmail.com>
References: <1adc5bd30911220847x4721314aqfe0e72594dd14a6a@mail.gmail.com>
Message-ID: <1adc5bd30911221314u673021c0s8f6b8f397485cee4@mail.gmail.com>

2009/11/22 Lukasz Kies <kiesiu at kiesiu.com>:
> rc-scripts-0.4.2.6-2 from Th test breaks localtime hwclock synchronization.
> In this version someone changed options for hwclock in case of
> localtime clock from --localtime to -l and in case of UTC clock from
> --utc to -u.
> The UTC change is correct but hwclock doesn't regonize -l option.
Glen, thanks for commit.

Regards,
Lukasz


From udvzsolt at gmail.com  Wed Nov 25 09:51:15 2009
From: udvzsolt at gmail.com (Zsolt Udvari)
Date: Wed, 25 Nov 2009 09:51:15 +0100
Subject: TeTeX and TeXLive
Message-ID: <760ece280911250051y51f395aar48bcaa1229f3f646@mail.gmail.com>

Hi all!

I'm working on TeXLive2009 and when anybody follows the changes, can
see, that I'm splitting the texlive packages to a noarch and an
arch-depend part (texlive-texmf.spec and texlive.spec). The packages
names don't change (not will be e.g. texlive-texmf-latex-math or
similar, only texlive-latex-math).
In texlive.spec and texlive-texmf.spec there are many tetex-* provides
(and obsoletes) because of compatibility with another, older packages
(which (build)requires tetex-*). I want remove these provides in
texlive.spec and texlive-texmf.spec, because these provides are a
little difficult and imho unnecessary and redundant (yesterday I
searched a provides-obsoletes-conlict about a half hour).
The texlive packages are in repos about a half year (as I remember)
and as I know, they work well. There are some difficulty with upgrade
from tetex to texlive but as I know, can solve these problems with
manual upgrade. And yes, texlive-packages need some more requires
(mostly in latex-* packages, but I don't use e.g. chemical packages so
I can't test them), so not perfect.

So, what I want?
>From the "developers": I want that the package "maintainers" check
his/her packages and their (build)requires and if necessary, update
the depends from tetex to texlive and increment the release (and test
the package, of course ;))
>From the "users" (and "developers" too ;)): if you use any TeX-system
and you use tetex now, please upgrade to texlive.

Thanks!

Zsolt


From glen at pld-linux.org  Wed Nov 25 10:33:01 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Wed, 25 Nov 2009 11:33:01 +0200
Subject: cvsnt dos eol stupidity (was: readded with -kb to keep CR/L...)
In-Reply-To: <200906211920.57141.glen@delfi.ee>
References: <packages_soundtouch_soundtouch_nosse.patch.1.2@pld-linux.org>
	<packages_soundtouch_soundtouch_nosse.patch.1.3@pld-linux.org>
	<200906211920.57141.glen@delfi.ee>
Message-ID: <200911251133.01506.glen@pld-linux.org>

On Sunday 21 June 2009 19:20:56 Elan Ruusam?e wrote:
> On Sunday 21 June 2009 19:11, hawk wrote:
> > - readded with -kb to keep CR/LF as required
>
> blah? undos the patched file(s) instead. reasons why are already discussed
> several times in this list.

http://www.cvsnt.org/manual/html/Substitution-modes.html

here seems to be the doc to control the eol style.

however i don't see a way to have mixed mode, so we should still go with 
approach of:

1. undos source
2. patch source with unix line endings.

or what you think?

and having binary file mode is no-no, as it will make diff feature in cvsweb 
unavailable.

-- 
glen


From patrys at pld-linux.org  Wed Nov 25 10:36:38 2009
From: patrys at pld-linux.org (Patryk Zawadzki)
Date: Wed, 25 Nov 2009 10:36:38 +0100
Subject: cvsnt dos eol stupidity (was: readded with -kb to keep CR/L...)
In-Reply-To: <200911251133.01506.glen@pld-linux.org>
References: <packages_soundtouch_soundtouch_nosse.patch.1.2@pld-linux.org>
	<packages_soundtouch_soundtouch_nosse.patch.1.3@pld-linux.org>
	<200906211920.57141.glen@delfi.ee>
	<200911251133.01506.glen@pld-linux.org>
Message-ID: <89b6ba3a0911250136n177a82a2va94c404fcedee530@mail.gmail.com>

2009/11/25 Elan Ruusam?e <glen at pld-linux.org>:
> http://www.cvsnt.org/manual/html/Substitution-modes.html
>
> here seems to be the doc to control the eol style.
>
> however i don't see a way to have mixed mode, so we should still go with
> approach of:
>
> 1. undos source
> 2. patch source with unix line endings.
>
> or what you think?

Switch to git / mercurial already? *hides*

-- 
Patryk Zawadzki


From glen at pld-linux.org  Wed Nov 25 11:30:15 2009
From: glen at pld-linux.org (Elan =?utf-8?q?Ruusam=C3=A4e?=)
Date: Wed, 25 Nov 2009 12:30:15 +0200
Subject: cvsnt dos eol stupidity (was: readded with -kb to keep CR/L...)
In-Reply-To: <89b6ba3a0911250136n177a82a2va94c404fcedee530@mail.gmail.com>
References: <packages_soundtouch_soundtouch_nosse.patch.1.2@pld-linux.org>
	<200911251133.01506.glen@pld-linux.org>
	<89b6ba3a0911250136n177a82a2va94c404fcedee530@mail.gmail.com>
Message-ID: <200911251230.15249.glen@pld-linux.org>

On Wednesday 25 November 2009 11:36:38 Patryk Zawadzki wrote:
> Switch to git / mercurial already? *hides*

i'd see first git.pld-linux.org operating for the developer community first, 
but apparently nobody is working towards that.

-- 
glen


From patrys at pld-linux.org  Wed Nov 25 13:16:18 2009
From: patrys at pld-linux.org (Patryk Zawadzki)
Date: Wed, 25 Nov 2009 13:16:18 +0100
Subject: cvsnt dos eol stupidity (was: readded with -kb to keep CR/L...)
In-Reply-To: <200911251230.15249.glen@pld-linux.org>
References: <packages_soundtouch_soundtouch_nosse.patch.1.2@pld-linux.org>
	<200911251133.01506.glen@pld-linux.org>
	<89b6ba3a0911250136n177a82a2va94c404fcedee530@mail.gmail.com>
	<200911251230.15249.glen@pld-linux.org>
Message-ID: <89b6ba3a0911250416l5cff725cv7c4dc76c0779a7f@mail.gmail.com>

2009/11/25 Elan Ruusam?e <glen at pld-linux.org>:
> On Wednesday 25 November 2009 11:36:38 Patryk Zawadzki wrote:
>> Switch to git / mercurial already? *hides*
> i'd see first git.pld-linux.org operating for the developer community first,
> but apparently nobody is working towards that.

It requires root access and I think I already gave you a step-by-step
solution :)

-- 
Patryk Zawadzki


From glen at pld-linux.org  Wed Nov 25 15:01:45 2009
From: glen at pld-linux.org (Elan =?utf-8?q?Ruusam=C3=A4e?=)
Date: Wed, 25 Nov 2009 16:01:45 +0200
Subject: cvsnt dos eol stupidity (was: readded with -kb to keep CR/L...)
In-Reply-To: <89b6ba3a0911250416l5cff725cv7c4dc76c0779a7f@mail.gmail.com>
References: <packages_soundtouch_soundtouch_nosse.patch.1.2@pld-linux.org>
	<200911251230.15249.glen@pld-linux.org>
	<89b6ba3a0911250416l5cff725cv7c4dc76c0779a7f@mail.gmail.com>
Message-ID: <200911251601.45444.glen@pld-linux.org>

On Wednesday 25 November 2009 14:16:18 Patryk Zawadzki wrote:
> 2009/11/25 Elan Ruusam?e <glen at pld-linux.org>:
> > On Wednesday 25 November 2009 11:36:38 Patryk Zawadzki wrote:
> >> Switch to git / mercurial already? *hides*
> >
> > i'd see first git.pld-linux.org operating for the developer community
> > first, but apparently nobody is working towards that.
>
> It requires root access and I think I already gave you a step-by-step
> solution :)

you could post it to your blog too, it has the same effect. i have no mana to 
setup it even if i have 300 root-s...

-- 
glen


From glen at pld-linux.org  Wed Nov 25 15:06:29 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Wed, 25 Nov 2009 16:06:29 +0200
Subject: TeTeX and TeXLive
In-Reply-To: <760ece280911250051y51f395aar48bcaa1229f3f646@mail.gmail.com>
References: <760ece280911250051y51f395aar48bcaa1229f3f646@mail.gmail.com>
Message-ID: <200911251606.30109.glen@pld-linux.org>

On Wednesday 25 November 2009 10:51:15 Zsolt Udvari wrote:
> So, what I want?
>
> From the "developers": I want that the package "maintainers" check
> his/her packages and their (build)requires and if necessary, update
> the depends from tetex to texlive and increment the release (and test
> the package, of course ;))
>
> From the "users" (and "developers" too ;)): if you use any TeX-system
> and you use tetex now, please upgrade to texlive.

isn't this this is too complicated for average developer (tm)?

how would he/she know what is the new name? 

imho it's better make some migration package for the upgrade process and
maintain it separately, like there exists X11.spec.

it could be also source for BR's to fill, maybe even adopt adapter.awk for that.

[1] http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/packages/X11/X11.spec?only_with_tag=AC-branch

-- 
glen


From udvzsolt at gmail.com  Wed Nov 25 17:02:50 2009
From: udvzsolt at gmail.com (Zsolt Udvari)
Date: Wed, 25 Nov 2009 17:02:50 +0100
Subject: TeTeX and TeXLive
In-Reply-To: <200911251606.30109.glen@pld-linux.org>
References: <760ece280911250051y51f395aar48bcaa1229f3f646@mail.gmail.com>
	<200911251606.30109.glen@pld-linux.org>
Message-ID: <20091125170250.2fa9b34b@pld-laptop>

> > From the "developers": I want that the package "maintainers" check
> > his/her packages and their (build)requires and if necessary, update
> > the depends from tetex to texlive and increment the release (and
> > test the package, of course ;))
> >
> > From the "users" (and "developers" too ;)): if you use any
> > TeX-system and you use tetex now, please upgrade to texlive.
> 
> isn't this this is too complicated for average developer (tm)?
Hm? I don't understand you. If a developer ("package maintainer")
updates and cares about foo.spec, (s)he knows that this package needs
or not any tetex-package.

> how would he/she know what is the new name? 
From tetex to texlive? In the most cases the name is "equal" (texlive-foo
instead of tetex-foo). Any cases: search in poldek which package provides
tetex-foo and can find that texlive-foo2 provides tetex-foo. Or this isn't
solution?

> imho it's better make some migration package for the upgrade process
> and maintain it separately, like there exists X11.spec.
So do you say that should be create texlive2008.spec?

Zsolt



From glen at pld-linux.org  Wed Nov 25 17:56:36 2009
From: glen at pld-linux.org (Elan =?iso-8859-1?q?Ruusam=E4e?=)
Date: Wed, 25 Nov 2009 18:56:36 +0200
Subject: TeTeX and TeXLive
In-Reply-To: <20091125170250.2fa9b34b@pld-laptop>
References: <760ece280911250051y51f395aar48bcaa1229f3f646@mail.gmail.com>
	<200911251606.30109.glen@pld-linux.org>
	<20091125170250.2fa9b34b@pld-laptop>
Message-ID: <200911251856.36479.glen@pld-linux.org>

On Wednesday 25 November 2009 18:02:50 Zsolt Udvari wrote:
> > isn't this this is too complicated for average developer (tm)?
>
> Hm? I don't understand you. If a developer ("package maintainer")
> updates and cares about foo.spec, (s)he knows that this package needs
> or not any tetex-package.

i update git-core.spec, i don't know a sh*t of tetex* crapolla. so i just 
disable the doc building then? i care for git-core as a program, not the 
madness behind documentation building. so i as git-core updater don't now 
anything which tetex is needed or is needed not whatsoever.

-- 
glen


From udvzsolt at gmail.com  Wed Nov 25 18:04:11 2009
From: udvzsolt at gmail.com (Zsolt Udvari)
Date: Wed, 25 Nov 2009 18:04:11 +0100
Subject: TeTeX and TeXLive
In-Reply-To: <200911251856.36479.glen@pld-linux.org>
References: <760ece280911250051y51f395aar48bcaa1229f3f646@mail.gmail.com>
	<200911251606.30109.glen@pld-linux.org>
	<20091125170250.2fa9b34b@pld-laptop>
	<200911251856.36479.glen@pld-linux.org>
Message-ID: <20091125180411.7e989dd5@pld-laptop>

> i update git-core.spec, i don't know a sh*t of tetex* crapolla. so i
> just disable the doc building then? i care for git-core as a program,
> not the madness behind documentation building. so i as git-core
> updater don't now anything which tetex is needed or is needed not
> whatsoever.

Ask me :D 
I've checked the git-core.spec at this moment, and as I see, no tetex* BR.

But if the most of developers say that the remove of tetex-provides is
a very bad idea, I don't remove them ;)

Zsolt


From z at xatka.net  Wed Nov 25 18:42:34 2009
From: z at xatka.net (=?iso-8859-2?Q?Pawe=B3?= Zuzelski)
Date: Wed, 25 Nov 2009 18:42:34 +0100
Subject: TeTeX and TeXLive
In-Reply-To: <20091125180411.7e989dd5@pld-laptop>
References: <760ece280911250051y51f395aar48bcaa1229f3f646@mail.gmail.com>
	<200911251606.30109.glen@pld-linux.org>
	<20091125170250.2fa9b34b@pld-laptop>
	<200911251856.36479.glen@pld-linux.org>
	<20091125180411.7e989dd5@pld-laptop>
Message-ID: <20091125174233.GA3823@davabel>

On Wed, 25 Nov 2009, Zsolt Udvari wrote:

> > i update git-core.spec, i don't know a sh*t of tetex* crapolla. so i
> > just disable the doc building then? i care for git-core as a program,
> > not the madness behind documentation building. so i as git-core
> > updater don't now anything which tetex is needed or is needed not
> > whatsoever.
> 
> Ask me :D 
> I've checked the git-core.spec at this moment, and as I see, no tetex* BR.
> 
> But if the most of developers say that the remove of tetex-provides is
> a very bad idea, I don't remove them ;)

Why don't we just update all specs on HEAD and DEVEL using some
automagic awk script?  If Provides work it should works too.

-- 
Regards,
Pawe?


From udvzsolt at gmail.com  Wed Nov 25 19:03:09 2009
From: udvzsolt at gmail.com (Zsolt Udvari)
Date: Wed, 25 Nov 2009 19:03:09 +0100
Subject: TeTeX and TeXLive
In-Reply-To: <20091125174233.GA3823@davabel>
References: <760ece280911250051y51f395aar48bcaa1229f3f646@mail.gmail.com>
	<200911251606.30109.glen@pld-linux.org>
	<20091125170250.2fa9b34b@pld-laptop>
	<200911251856.36479.glen@pld-linux.org>
	<20091125180411.7e989dd5@pld-laptop>
	<20091125174233.GA3823@davabel>
Message-ID: <20091125190309.0ffaeec6@pld-laptop>

> Why don't we just update all specs on HEAD and DEVEL using some
> automagic awk script?  If Provides work it should works too.
I'm not an awk-guru :)

Zsolt



From freetz at gmx.net  Wed Nov 25 19:06:02 2009
From: freetz at gmx.net (Fryderyk Dziarmagowski)
Date: Wed, 25 Nov 2009 19:06:02 +0100
Subject: packages: gnome-mplayer/gnome-mplayer.spec - BR: GConf2,
	GConf2-devel, curl...
In-Reply-To: <packages_gnome_mplayer_gnome_mplayer.spec.1.23@pld-linux.org>
References: <packages_gnome_mplayer_gnome_mplayer.spec.1.22@pld-linux.org>
	<packages_gnome_mplayer_gnome_mplayer.spec.1.23@pld-linux.org>
Message-ID: <20091125190602.81066af0.freetz@gmx.net>

On Wed, 25 Nov 2009 17:43:38 +0100
sparky <sparky at pld-linux.org> wrote:

> Author: sparky                       Date: Wed Nov 25 16:43:38 2009 GMT
> Module: packages                      Tag: HEAD
> ---- Log message:
> - BR: GConf2, GConf2-devel, curl-devel, gnome-power-manager, pulseaudio, which

What is the idea behind adding tons of wrong BRs?

-- 
Fryderyk Dziarmagowski


From sparky at pld-linux.org  Wed Nov 25 19:17:20 2009
From: sparky at pld-linux.org (Przemyslaw Iskra)
Date: Wed, 25 Nov 2009 19:17:20 +0100
Subject: packages: gnome-mplayer/gnome-mplayer.spec - BR: GConf2,
	GConf2-devel, curl...
In-Reply-To: <20091125190602.81066af0.freetz@gmx.net>
References: <packages_gnome_mplayer_gnome_mplayer.spec.1.22@pld-linux.org>
	<packages_gnome_mplayer_gnome_mplayer.spec.1.23@pld-linux.org>
	<20091125190602.81066af0.freetz@gmx.net>
Message-ID: <20091125181720.GA21690@pld-linux.org>

On Wed, Nov 25, 2009 at 07:06:02PM +0100, Fryderyk Dziarmagowski wrote:
> On Wed, 25 Nov 2009 17:43:38 +0100
> sparky <sparky at pld-linux.org> wrote:
> 
> > Author: sparky                       Date: Wed Nov 25 16:43:38 2009 GMT
> > Module: packages                      Tag: HEAD
> > ---- Log message:
> > - BR: GConf2, GConf2-devel, curl-devel, gnome-power-manager, pulseaudio, which
> 
> What is the idea behind adding tons of wrong BRs?

Unforunatelly those aren't wrong, and fixing configure doesn't really
seem worth it.


FLATVOL=FALSE
if test -x `which pulseaudio`; then
        PAVER=`pulseaudio --version | sed -e 's/pulseaudio 0.9.//'`
        if test $PAVER -gt 14; then
            FLATVOL=TRUE
        fi
fi
AC_SUBST(FLATVOL)

if test -x `which gnome-power-manager`; then
        GPMVER=`gnome-power-manager --version | sed -e 's/Version 2.//' | cut -b1-2`
        if test $GPMVER -ge 26; then
            AC_DEFINE(SM_INHIBIT, 1, [Defined if you are using
gnome-power-manager 2.26 or higher])
        fi
        if test $GPMVER -lt 26; then
            AC_DEFINE(SS_INHIBIT, 1, [Defined if you are using
gnome-power-manager below 2.26 ])
        fi

fi


^- there are which, pulseaudio and gnome-power-manager

curl-devel is required for libmusicbrainz3

And GConf2 is required because build fails without it.



-- 
 ____  Sparky{PI] -- Przemyslaw _  ___  _  _  ........... LANG...Pl..Ca..Es..En
/____) ___  ___  _ _ || Iskra  |  | _ \| |  | : WWW........ppcrcd.pld-linux.org
\____\| -_)'___| ||^'||//\\// <   |  _/| |  | : JID......sparky<at>jabberes.org
(____/||   (_-_|_||  ||\\ ||   |_ |_|  |_| _| : Mail....sparky<at>pld-linux.org


From jajcus at jajcus.net  Sat Nov 28 16:22:57 2009
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Sat, 28 Nov 2009 16:22:57 +0100
Subject: TeXLive, Lilypond and /usr/share/texmf/fonts/{source,tfm,type1} dirs
Message-ID: <20091128152257.GB3586@lolek.nigdzie>

Hello,

lilypond cannot be installed because of:

error: lilypond-2.12.2-1.i686: req /usr/share/texmf/fonts/source not found
error: lilypond-2.12.2-1.i686: req /usr/share/texmf/fonts/tfm not found
error: lilypond-2.12.2-1.i686: req /usr/share/texmf/fonts/type1 not found

Are these directories still correct? Which package should provide them?

Greets,
        Jacek


From udvzsolt at gmail.com  Sat Nov 28 16:35:19 2009
From: udvzsolt at gmail.com (Zsolt Udvari)
Date: Sat, 28 Nov 2009 16:35:19 +0100
Subject: TeXLive, Lilypond and /usr/share/texmf/fonts/{source,tfm,type1}
	dirs
In-Reply-To: <20091128152257.GB3586@lolek.nigdzie>
References: <20091128152257.GB3586@lolek.nigdzie>
Message-ID: <20091128163519.3966a861@pld-laptop>

> lilypond cannot be installed because of:
> 
> error: lilypond-2.12.2-1.i686: req /usr/share/texmf/fonts/source not
> found error: lilypond-2.12.2-1.i686: req /usr/share/texmf/fonts/tfm
> not found error: lilypond-2.12.2-1.i686:
> req /usr/share/texmf/fonts/type1 not found
> 
> Are these directories still correct? Which package should provide
> them?

You should use /usr/share/texmf-dist directory. 
http://tug.org/texlive/doc/texlive-en/texlive-en.html#x1-110002.3

Zsolt



From sparky at pld-linux.org  Sat Nov 28 19:14:24 2009
From: sparky at pld-linux.org (Przemyslaw Iskra)
Date: Sat, 28 Nov 2009 19:14:24 +0100
Subject: packages: Firebird/Firebird.spec - updated last commit log
In-Reply-To: <packages_Firebird_Firebird.spec.1.72@pld-linux.org>
References: <packages_Firebird_Firebird.spec.1.71@pld-linux.org>
	<packages_Firebird_Firebird.spec.1.72@pld-linux.org>
Message-ID: <20091128181423.GA22159@pld-linux.org>

On Sat, Nov 28, 2009 at 05:20:01PM +0100, charles wrote:
> Author: charles                      Date: Sat Nov 28 16:20:01 2009 GMT
> Module: packages                      Tag: HEAD
> ---- Log message:
> - updated last commit log

> +Revision 1.72  2009/11/28 16:19:56  charles
> +- updated last commit log
> +
>  Revision 1.71  2009/11/28 14:04:14  charles
>  - adapterized
> +- added fb_lock_print,gbak,gdef,gds_drop,gfix,gpre,gsec,gsplit,gstat,nbackup symlinks


Could you please in such cases also repeat it in cvs commit message ?
I think more people depend on "cvs log" command than %changelog from spec.

-- 
 ____  Sparky{PI] -- Przemyslaw _  ___  _  _  ........... LANG...Pl..Ca..Es..En
/____) ___  ___  _ _ || Iskra  |  | _ \| |  | : WWW........ppcrcd.pld-linux.org
\____\| -_)'___| ||^'||//\\// <   |  _/| |  | : JID......sparky<at>jabberes.org
(____/||   (_-_|_||  ||\\ ||   |_ |_|  |_| _| : Mail....sparky<at>pld-linux.org


From kkrenski at gmail.com  Sat Nov 28 19:30:27 2009
From: kkrenski at gmail.com (Charles)
Date: Sat, 28 Nov 2009 19:30:27 +0100
Subject: packages: Firebird/Firebird.spec - updated last commit log
In-Reply-To: <20091128181423.GA22159@pld-linux.org>
References: <packages_Firebird_Firebird.spec.1.71@pld-linux.org>
	<packages_Firebird_Firebird.spec.1.72@pld-linux.org>
	<20091128181423.GA22159@pld-linux.org>
Message-ID: <200911281930.27331.kkrenski@gmail.com>

Dnia sobota, 28 listopada 2009, Przemyslaw Iskra napisa?:
> > +Revision 1.72 ?2009/11/28 16:19:56 ?charles
> > +- updated last commit log
> > +
> > ?Revision 1.71 ?2009/11/28 14:04:14 ?charles
> > ?- adapterized
> > +- added fb_lock_print,gbak,gdef,gds_drop,gfix,gpre,gsec,gsplit,gstat,nbackup symlinks
>
> Could you please in such cases also repeat it in cvs commit message ?
> I think more people depend on "cvs log" command than %changelog from
> spec.

Right.
That makes sense.

-- 
Karol Krenski