old links to patches
On Thursday 07 May 2009 12:40:42 Tomasz Pala wrote: BTW there's one more problem - there are http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/blabla links to patches floating around which point to nowhere now... please give (at least) one sample, so i could write 404 handler in apache to solve this problem. -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
misc scripts in cvs
On Wednesday 29 April 2009 14:08:36 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. doing cvs up revealed what other non-spec files were present, where they are now? so, where should these go, also some misc scripts in SOURCES like: kdediff.sh, kde4diff.sh, where those should end up? /scripts? /packages? g...@builder-ac pld/SPECS $ grep 'is no longer' /tmp/ss cvs server: .cvsignore is no longer in the repository cvs server: COPYING is no longer in the repository cvs server: R-spec.sh is no longer in the repository cvs server: adapter is no longer in the repository cvs server: adapter.awk is no longer in the repository cvs server: additional-md5sums is no longer in the repository cvs server: apt-get-buildrequires is no longer in the repository cvs server: bcond-list is no longer in the repository cvs server: builder is no longer in the repository cvs server: buildrpm_request is no longer in the repository cvs server: check-cvs-sync is no longer in the repository cvs server: check-ftp-sync is no longer in the repository cvs server: check_fresh is no longer in the repository cvs server: compile.sh is no longer in the repository cvs server: fetchsrc_request is no longer in the repository cvs server: find-spec is no longer in the repository cvs server: ftplinks.sh is no longer in the repository cvs server: getsrc is no longer in the repository cvs server: getsrcurl is no longer in the repository cvs server: hamcrest.spec is no longer in the repository cvs server: hardcoded-pkgs is no longer in the repository cvs server: makegen is no longer in the repository cvs server: md5 is no longer in the repository cvs server: mirrors is no longer in the repository cvs server: mysql-connector-j.spec is no longer in the repository cvs server: new-cpan.sh is no longer in the repository cvs server: nps.spec is no longer in the repository cvs server: old2newbconds.awk is no longer in the repository cvs server: optflags-test is no longer in the repository cvs server: package-opts is no longer in the repository cvs server: patchtool.pl is no longer in the repository cvs server: pearize.sh is no longer in the repository cvs server: perl-autoup is no longer in the repository cvs server: pldnotify.awk is no longer in the repository cvs server: poldek-get-buildrequires is no longer in the repository cvs server: relup.sh is no longer in the repository cvs server: repackage.sh is no longer in the repository cvs server: review.py is no longer in the repository cvs server: rollback is no longer in the repository cvs server: rpmdb-checkdir.sh is no longer in the repository cvs server: rsget2.spec is no longer in the repository cvs server: sb.sh is no longer in the repository cvs server: sed_to_patch.pl is no longer in the repository cvs server: spec_utf8 is no longer in the repository cvs server: specparser.pl is no longer in the repository cvs server: srcwrap is no longer in the repository [template*.spec omited] cvs server: updatelib.sh is no longer in the repository cvs server: utf8_check.py is no longer in the repository cvs server: verup.sh is no longer in the repository cvs server: workcleanup.sh is no longer in the repository cvs server: xemacs-adapter is no longer in the repository cvs server: xemacs-adapter-template is no longer in the repository cvs server: xemacs-adapter.awk is no longer in the repository g...@builder-ac pld/SPECS $ -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: old links to patches
On Fri, May 08, 2009 at 12:22:03 +0300, Elan Ruusamäe wrote: http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/blabla links to patches floating around which point to nowhere now... please give (at least) one sample, so i could write 404 handler in apache to solve this problem. http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/quagga-view_commands.patch I've provided them always in this form. -- Tomasz Pala go...@pld-linux.org ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: topdir macro
On Sunday 03 May 2009 13:31:15 Arkadiusz Miskiewicz wrote:
It's nice bit it will break in a case when you use some .src.rpm and
install it. It should be installed in standard place - rpm/{SOURCES,SPECS}
not in our packages.
why is it so? i mean why you need it being installed in rpm/{SOURCES,SPECS}?
you can't build such pkg anyway, if building requires sources/specs being in
pld layout and otoh no path is hardcoded, the same macros are used in
building as in installing src.rpm...
--
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: old links to patches
On Friday 08 May 2009 12:28:13 Tomasz Pala wrote: On Fri, May 08, 2009 at 12:22:03 +0300, Elan Ruusamäe wrote: http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/blabla links to patches floating around which point to nowhere now... please give (at least) one sample, so i could write 404 handler in apache to solve this problem. http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/quagga-view_commands.patch I've provided them always in this form. i mean, a url to resource which contains link to _that_ link. -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: old links to patches
On Fri, May 08, 2009 at 12:33:46 +0300, Elan Ruusamäe wrote: please give (at least) one sample, so i could write 404 handler in apache to solve this problem. i mean, a url to resource which contains link to _that_ link. Like this? http://lists.quagga.net/pipermail/quagga-dev/2009-April/006507.html -- Tomasz Pala go...@pld-linux.org ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: old links to patches
On Friday 08 May 2009 13:19:04 Tomasz Pala wrote: On Fri, May 08, 2009 at 12:33:46 +0300, Elan Ruusamäe wrote: please give (at least) one sample, so i could write 404 handler in apache to solve this problem. i mean, a url to resource which contains link to _that_ link. Like this? http://lists.quagga.net/pipermail/quagga-dev/2009-April/006507.html yep. for now added redirect rules: RedirectMatch permanent ^/cgi-bin/cvsweb/SOURCES/(.*)$ http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES.old/$1 RedirectMatch permanent ^/cgi-bin/cvsweb\.cgi/SOURCES/(.*)$ http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/SOURCES.old/$1 is this sufficent, or we should rather redirect to new location in /packages? i mean if you gave old link, then you likely want to point it to the resource available at that time, which this SOURCES.old redirection satisfies. however this will all go void if the SOURCES.old tree is removed someday. -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: misc scripts in cvs
Elan =?iso-8859-1?q?Ruusam=E4e?= wrote: On Wednesday 29 April 2009 14:08:36 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. doing cvs up revealed what other non-spec files were present, where they are now? so, where should these go, also some misc scripts in SOURCES like: kdediff.sh, kde4diff.sh, where those should end up? /scripts? /packages? Topdir packages in IMVHO the worst place for them. /packages/scripts or /packages/SCRIPTS ? -- === Andrzej M. Krzysztofowicz an...@mif.pg.gda.pl phone (48)(58) 347 19 36 Faculty of Applied Phys. Math., Gdansk University of Technology ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: packages: transmission/transmission.spec - gui-qt subpackage (there is a Qt...
On Fri, May 08, 2009 at 11:34:22PM +0200, uzsolt wrote:
Author: uzsolt Date: Fri May 8 21:34:22 2009 GMT
Module: packages Tag: HEAD
Log message:
- gui-qt subpackage (there is a Qt-based client)
- rel 2
+cd qt
+qmake-qt4
+%{__sed} -i s...@^cflags.*=.*@CFLAGS = %{rpmcflags} -I/usr/include/openssl
$(DEFINES)@ Makefile
+%{__sed} -i s...@^cxxflags.*=.*@CXXFLAGS = %{rpmcxxflags}
-I/usr/include/openssl $(DEFINES)@ Makefile
+%{__make}
That's not what we do.
You should rather pass those values to __make.
--
Sparky{PI] -- Przemyslaw _ ___ _ _ ... LANG...Pl..Ca..Es..En
/) ___ ___ _ _ || Iskra | | _ \| | | : WWWppcrcd.pld-linux.org
\\| -_)'___| ||^'||//\\//| _/| | | : JID..sparkyatjabberes.org
(/|| (_-_|_|| ||\\ || |_ |_| |_| _| : Mailsparkyatpld-linux.org
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
