Re: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Wed, 07 Sep 2005, wrobell wrote: > On Wed, 2005-09-07 at 11:03 +0200, Jan Rekorajski wrote: > > Example: http://svn.pld-linux.org/svn/rc-scripts > > I want to keep only trunk, branches and _some_ tags, tell me how to do > > it, and how to prevent svn up from getting all tags. > > svn up trunk? > svn up tags/tagireallywant? > > come on... Ok, that's solved then, thanks. One more question - how to do 'svn up' in directory where I did checkouts so it will update all checked subdirs? With cvs all I need to do is `mkdir CVS ; echo $CVSROOT > CVS/Root ; cvs up` A recipe for svn much appreciated :) > > And the royal PITA, which svn is, is not worth it. > > ... it is really hard to discuss with such arguments, which seem > to be matter of taste. > > i think (let's skip svn for now), we need: > - to keep history of tags and branches ok, I guess all versioning systems must have it, or do you mean dead/deleted tags and branches? What for? > - atomic commit (so we can commit patches and specs with one move > and revert it easily later if there is a need) Example? > - ability to rename specs and patches without pain and loosing > information and _without_administrator_ help Maybe, but do we really do this that often? > - check changes without making connection to remote server And svn solves it how? > these are my problems with cvs. svn solves them. > > svn gives us some advantages. disadvantages? any real, which makes life > really painful? let's talk but without "royal PITA", "i do not care > for lost information", "i do not care for renaming", etc. please. One BIG disadvantege is that we will have to reorganize the entire repo into "one package" = "one svn dir" layout. And then it's either a fscking lot of copying svn-local-repo <-> ~/rpm/* or constant editing of ~/.rpmmacros. With current layout I can just checkout entire SPECS and SOURCES and work with any package on any branch easily. And then, what "lost information"? And the argument about renaming is just making me laugh, we have more than 9400 specs, we needed to rename how much of them? 10? 20? Come on. > then, if svn is not solution for us, then what other alternatives > we can use? let's think about it, because cvs is not solution > for us. Why it is not? I work with it from the beggining and I don't feel any need to switch, I haven't yet seen a versioning system that would give enough advantages that I'd consider switching. Janek -- Jan Rękorajski| ALL SUSPECTS ARE GUILTY. PERIOD! bagginsmimuw.edu.pl | OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY? BOFH, MANIAC | -- TROOPS by Kevin Rubio ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn...
On Wed, 07 Sep 2005, Paweł Sakowski wrote: > On Wed, 2005-09-07 at 10:20 +0100, wrobell wrote: > > - atomic commit (so we can commit patches and specs with one move > > and revert it easily later if there is a need) > > A propos reverting. > > One thing that we use (need?) and svn lacks is support for $Log$. So, we > would be missing autogenerated %changelog. However, I personally would > be happy to get rid of it, because: > > - it only reflects commits to the spec, not to the patches (and seeing > that the only difference between two releases is "rel up" is confusing > and doesn't help one bit) Smash the uneducated ;) Seriously having or not changelog in spec will not change some people habbit of putting dumb comments. But, most of the time changelog in spec helps. > - it makes it impossible to revert by `cvs up -j` (you lose changelog > entries) Is it really that important? After 6 years of work with our CVS I can't remember needing it. > The question is: is there anyone who uses/needs `rpm -q --changelog` > and/or wants/needs to have the changelog available offline? I would be > happy with `svn log` to see the changelog. Did someone said something about disconnected work with svn? Come on svn fans, you're contradicting yourselves. Janek -- Jan Rękorajski| ALL SUSPECTS ARE GUILTY. PERIOD! bagginsmimuw.edu.pl | OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY? BOFH, MANIAC | -- TROOPS by Kevin Rubio ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: SPECS: rsnapshot.spec - requires DirHandle.pm, so full perl depend...
ehm, perl contains no files except %doc
don't you mean perl-modules?
and, instead of manually filling runtime deps, include macros.perl and let rpm
fill the deps?
On Wednesday 07 September 2005 22:47, aredridel wrote:
> Author: aredridelDate: Wed Sep 7 19:47:17 2005 GMT
> Module: SPECS Tag: HEAD
> Log message:
> - requires DirHandle.pm, so full perl dependency
>
> Files affected:
> SPECS:
>rsnapshot.spec (1.13 -> 1.14)
>
> Diffs:
>
>
> Index: SPECS/rsnapshot.spec
> diff -u SPECS/rsnapshot.spec:1.13 SPECS/rsnapshot.spec:1.14
> --- SPECS/rsnapshot.spec:1.13 Tue Aug 30 20:37:03 2005
> +++ SPECS/rsnapshot.spec Wed Sep 7 21:47:11 2005
> @@ -9,7 +9,7 @@
> Source0: http://www.rsnapshot.org/downloads/%{name}-%{version}.tar.gz
> # Source0-md5: b27d90886b25d0e160b267f98c605aec
> URL: http://www.rsnapshot.org/
> -Requires:perl-base
> +Requires:perl
> Requires:rsync
> BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n)
>
> @@ -52,6 +52,9 @@
> All persons listed below can be reached at @pld-linux.org
>
> $Log$
> +Revision 1.14 2005/09/07 19:47:11 aredridel
> +- requires DirHandle.pm, so full perl dependency
> +
> Revision 1.13 2005/08/30 18:37:03 darekr
> - sort verify() flags; License: GPL v2
>
>
>
> CVS-web:
> http://cvs.pld-linux.org/SPECS/rsnapshot.spec?r1=1.13&r2=1.14&f=u
>
> ___
> pld-cvs-commit mailing list
> pld-cvs-commit@lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
--
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn...
On Wed, Sep 07, 2005 at 06:01:30PM +0200, Paweł Sakowski wrote: > The question is: is there anyone who uses/needs `rpm -q --changelog` > and/or wants/needs to have the changelog available offline? I would be > happy with `svn log` to see the changelog. Not that I use `rpm -q changelog`, but I find it comfortable to have a list of recent changes directly in spec. -- http://www.mysza.eu.org/ | Everybody needs someone sure, someone true, PLD Linux developer | Everybody needs some solid rock, I know I do. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn...
On Wed, 2005-09-07 at 10:20 +0100, wrobell wrote: > - atomic commit (so we can commit patches and specs with one move > and revert it easily later if there is a need) A propos reverting. One thing that we use (need?) and svn lacks is support for $Log$. So, we would be missing autogenerated %changelog. However, I personally would be happy to get rid of it, because: - it only reflects commits to the spec, not to the patches (and seeing that the only difference between two releases is "rel up" is confusing and doesn't help one bit) - it makes it impossible to revert by `cvs up -j` (you lose changelog entries) The question is: is there anyone who uses/needs `rpm -q --changelog` and/or wants/needs to have the changelog available offline? I would be happy with `svn log` to see the changelog. -- Paweł Sakowski <[EMAIL PROTECTED]> PLD Linux Distribution ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Wed, 2005-09-07 at 16:51 +0200, Tomasz Pala wrote: > On Wed, Sep 07, 2005 at 10:20:54AM +0100, wrobell wrote: > > > > svn gives us some advantages. disadvantages? any real, which makes life > > really painful? > > How to resolve conflict? I've got a situation: > > ~: vi blabla > ~: svn ci blabla > snv reports conflict here > [fixing it manually] oops sorry... svn resolve missing here > ~: svn ci blabla > svn reports there's unresolved conflict wrobell <[EMAIL PROTECTED]> ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Wed, 2005-09-07 at 16:51 +0200, Tomasz Pala wrote: > On Wed, Sep 07, 2005 at 10:20:54AM +0100, wrobell wrote: > > > > svn gives us some advantages. disadvantages? any real, which makes life > > really painful? > > How to resolve conflict? I've got a situation: > > ~: vi blabla > ~: svn ci blabla > snv reports conflict here svn up missing here? > [fixing it manually] > ~: svn ci blabla > svn reports there's unresolved conflict wrobell <[EMAIL PROTECTED]> ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Wed, Sep 07, 2005 at 10:20:54AM +0100, wrobell wrote: > > svn gives us some advantages. disadvantages? any real, which makes life > really painful? How to resolve conflict? I've got a situation: ~: vi blabla ~: svn ci blabla snv reports conflict here [fixing it manually] ~: svn ci blabla svn reports there's unresolved conflict -- Tom Pala <[EMAIL PROTECTED]> http://vfmg.sourceforge.net/ http://tccs.sourceforge.net/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: pam split
On Wed, 7 Sep 2005, Elan [iso-8859-1] Ruusamäe wrote:
> anybody against splitting pam to pam and pam-libs?
>
> # rpm -Uhv pam-0.80.1-1.amd64.rpm
> Preparing...### [100%]
> file /etc/security/consoles from install of pam-0.80.1-1 conflicts
> with file from package pam-0.79.1-4
> file /etc/security/limits.conf from install of pam-0.80.1-1 conflicts
> with file from package pam-0.79.1-4
> # rpm -q pam --qf '%{name}-%{epoch}:%{version}-%{release}.%{arch}\n'
> pam-0:0.79.1-4.amd64
> pam-0:0.79.1-4.athlon
>
> so i could have single pam package, with config, doc, data files, and
> two pam-libs from different arches
Yes, should be ok.
There is a lot of such a things...
--
pozdr. Paweł Gołaszewski jid:bluesjabbergdapl
--
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.
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
pam split
hi
anybody against splitting pam to pam and pam-libs?
# rpm -Uhv pam-0.80.1-1.amd64.rpm
Preparing...### [100%]
file /etc/security/consoles from install of pam-0.80.1-1 conflicts with
file from package pam-0.79.1-4
file /etc/security/limits.conf from install of pam-0.80.1-1 conflicts
with file from package pam-0.79.1-4
# rpm -q pam --qf '%{name}-%{epoch}:%{version}-%{release}.%{arch}\n'
pam-0:0.79.1-4.amd64
pam-0:0.79.1-4.athlon
so i could have single pam package, with config, doc, data files, and two
pam-libs from different arches
--
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: mythtv.spec
On Wednesday 07 September 2005 01:58, Krystian T wrote:
> Hi
> I have built mythtv.spec --without nvidia and it's failed
> (X11-driver-nvidia is needed)
> I have looked in spec and I find
> %{?with_nvidia:BuildRequires: X11-driver-nvidia-devel}
> %{?with_opengl:BuildRequires: X11-driver-nvidia-devel}
>
> In second line IMHO must be X11-OpenGL-devel
replaced that all with xvmc wrapper. could you test does it (still) work?
--
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Wed, 2005-09-07 at 11:30 +0200, Arkadiusz Miskiewicz wrote:
> On Wednesday 07 of September 2005 11:20, wrobell wrote:
>
> > i think (let's skip svn for now), we need:
> > - atomic commit (so we can commit patches and specs with one move
> > and revert it easily later if there is a need)
> - easier work on branches without messing the way it recently happened with
> some patches used by k(l)ex.spec and kernel.spec at the same time
>
> these two things are most important for me
I'll add checking the changes two tags/branches (both spec and patches,
either as `cvs log` or `cvs diff`). Impossible now without visual
inspection of the spec for a list of {exist,{dis,}appear}ing patches.
Oh, and it's kindda sick that we need a script of 1781 lines to simply
fetch a given version (spec+patches).
--
Paweł Sakowski <[EMAIL PROTECTED]>
PLD Linux Distribution
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Wed, 2005-09-07 at 11:03 +0200, Jan Rekorajski wrote: > > you do _not_ have to keep _all_ tags/branches locally. > > Really? How? > Example: http://svn.pld-linux.org/svn/rc-scripts > I want to keep only trunk, branches and _some_ tags, tell me how to do > it, and how to prevent svn up from getting all tags. svn co http://svn.pld-linux.org/svn/rc-scripts/trunk rc-scripts svn co http://svn.pld-linux.org/svn/rc-scripts/tags/0.4.0.12 staroć -- Paweł Sakowski <[EMAIL PROTECTED]> PLD Linux Distribution ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Wednesday 07 of September 2005 11:20, wrobell wrote: > i think (let's skip svn for now), we need: > - atomic commit (so we can commit patches and specs with one move > and revert it easily later if there is a need) - easier work on branches without messing the way it recently happened with some patches used by k(l)ex.spec and kernel.spec at the same time these two things are most important for me > wrobell <[EMAIL PROTECTED]> -- Arkadiusz MiśkiewiczPLD/Linux Team http://www.t17.ds.pwr.wroc.pl/~misiek/ http://ftp.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: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Wed, 2005-09-07 at 11:03 +0200, Jan Rekorajski wrote: > On Wed, 07 Sep 2005, wrobell wrote: > > > On Tue, 2005-09-06 at 19:27 +0200, Jan Rekorajski wrote: > > > On Tue, 06 Sep 2005, wrobell wrote: > > > > > > > On Tue, 2005-09-06 at 18:46 +0200, Michal Kochanowicz wrote: > > > > > On Tue, Sep 06, 2005 at 05:32:50PM +0100, wrobell wrote: > > > > > > let's start new war... > > > > > > > > > > > > what about moving repo to svn? > > > > > > > > > > Any reasons? SVN sucks a big one. > > > > > > > > svn diff without performing connection to remote server. > > > > > > At the cost of keeping ALL tags/branches locally. You're joking. > > > > > > [EMAIL PROTECTED] rpm]$ du -hs SOURCES SPECS > > > 959MSOURCES > > > 63M SPECS > > > > you do _not_ have to keep _all_ tags/branches locally. > > Really? How? > Example: http://svn.pld-linux.org/svn/rc-scripts > I want to keep only trunk, branches and _some_ tags, tell me how to do > it, and how to prevent svn up from getting all tags. svn up trunk? svn up tags/tagireallywant? come on... > > > > i think that cvs really sucks. so... any alternatives? > > > > > > There is nothing better :/ > > > > with cvs we are loosing some information (i.e. deleted branches > > and tags). svn allows us to track it _easily_. > And the royal PITA, which svn is, is not worth it. ... it is really hard to discuss with such arguments, which seem to be matter of taste. i think (let's skip svn for now), we need: - to keep history of tags and branches - atomic commit (so we can commit patches and specs with one move and revert it easily later if there is a need) - ability to rename specs and patches without pain and loosing information and _without_administrator_ help - check changes without making connection to remote server these are my problems with cvs. svn solves them. svn gives us some advantages. disadvantages? any real, which makes life really painful? let's talk but without "royal PITA", "i do not care for lost information", "i do not care for renaming", etc. please. then, if svn is not solution for us, then what other alternatives we can use? let's think about it, because cvs is not solution for us. wrobell <[EMAIL PROTECTED]> ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Wed, 07 Sep 2005, wrobell wrote: > On Tue, 2005-09-06 at 19:27 +0200, Jan Rekorajski wrote: > > On Tue, 06 Sep 2005, wrobell wrote: > > > > > On Tue, 2005-09-06 at 18:46 +0200, Michal Kochanowicz wrote: > > > > On Tue, Sep 06, 2005 at 05:32:50PM +0100, wrobell wrote: > > > > > let's start new war... > > > > > > > > > > what about moving repo to svn? > > > > > > > > Any reasons? SVN sucks a big one. > > > > > > svn diff without performing connection to remote server. > > > > At the cost of keeping ALL tags/branches locally. You're joking. > > > > [EMAIL PROTECTED] rpm]$ du -hs SOURCES SPECS > > 959MSOURCES > > 63M SPECS > > you do _not_ have to keep _all_ tags/branches locally. Really? How? Example: http://svn.pld-linux.org/svn/rc-scripts I want to keep only trunk, branches and _some_ tags, tell me how to do it, and how to prevent svn up from getting all tags. > > > i think that cvs really sucks. so... any alternatives? > > > > There is nothing better :/ > > with cvs we are loosing some information (i.e. deleted branches > and tags). svn allows us to track it _easily_. And the royal PITA, which svn is, is not worth it. Janek -- Jan Rękorajski| ALL SUSPECTS ARE GUILTY. PERIOD! bagginsmimuw.edu.pl | OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY? BOFH, MANIAC | -- TROOPS by Kevin Rubio ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Tue, 2005-09-06 at 19:27 +0200, Jan Rekorajski wrote: > On Tue, 06 Sep 2005, wrobell wrote: > > > On Tue, 2005-09-06 at 18:46 +0200, Michal Kochanowicz wrote: > > > On Tue, Sep 06, 2005 at 05:32:50PM +0100, wrobell wrote: > > > > let's start new war... > > > > > > > > what about moving repo to svn? > > > > > > Any reasons? SVN sucks a big one. > > > > svn diff without performing connection to remote server. > > At the cost of keeping ALL tags/branches locally. You're joking. > > [EMAIL PROTECTED] rpm]$ du -hs SOURCES SPECS > 959MSOURCES > 63M SPECS you do _not_ have to keep _all_ tags/branches locally. > > i think that cvs really sucks. so... any alternatives? > > There is nothing better :/ with cvs we are loosing some information (i.e. deleted branches and tags). svn allows us to track it _easily_. wrobell <[EMAIL PROTECTED]> ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: cvs vs svn... (Re: SOURCES: ghostscript-afpl-am.patch (NEW), ghostscript-afpl-ijs_pkg...)
On Tue, 2005-09-06 at 20:30 +0200, Paweł Gołaszewski wrote: > On Tue, 6 Sep 2005, wrobell wrote: > > > Author: djurban Date: Tue Sep 6 16:24:57 2005 GMT > > > Module: SOURCES Tag: HEAD > > > Log message: > > > - from ghostscript.spec's HEAD > > > - lost the logs, but i dont have time to mail the commands for all > > > those files to cvs admins > > [...] > > > > let's start new war... > > > > what about moving repo to svn? > > no. > > If you really want to move - find something that gives _real_ advantages. can you _define_ "real advantages", please? wrobell <[EMAIL PROTECTED]> ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
