Re: gedit2 (Re: CVS rename for nautilussvn)
2012/5/6 Elan Ruusamäe g...@pld-linux.org: feel free to merge gedit2.spec to gedit.spec (and drop the former), just remember to handle obsoletes properly As a latecomer to CVS (backporting my knowledge of VCS from subversion, git, etc) I am not sure which button to push here. Since these two specs aren't a branch scenario, merge doesn't seem like the right option to me and I wouldn't know how to do it if it was. Shouldn't this be 1) remove the current gedit module 2) rename gedit2 to gedit and 3) cleanup the spec, setup obsoletes, and go through other specs for dependency issues? If so, I can take care of #3 if somebody else does the cvs server side stuff in #1 and #2. If not, then I have no idea what I'm doing. Caleb ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: gedit2 (Re: CVS rename for nautilussvn)
On 07.05.2012 15:01, Caleb Maclennan wrote: 2012/5/6 Elan Ruusamäeg...@pld-linux.org: feel free to merge gedit2.spec to gedit.spec (and drop the former), just remember to handle obsoletes properly As a latecomer to CVS (backporting my knowledge of VCS from subversion, git, etc) I am not sure which button to push here. Since these two specs aren't a branch scenario, merge doesn't seem like the right option to me and I wouldn't know how to do it if it was. Shouldn't this be 1) remove the current gedit module 2) rename gedit2 to gedit and 3) cleanup the spec, setup obsoletes, and go through other specs for dependency issues? merging history for same file is not possible in cvs (without excessive *,v file hacking). so the removing gedit module could be replaced with renaming gedit module as otherwise you end up with same *,v file again: 1. rename gedit dir to gedit0 in cvs server side and optionally drop it client side 2. rename gedit2 dir to gedit in cvs server side, and adjust names in files on cvs client side If so, I can take care of #3 if somebody else does the cvs server side stuff in #1 and #2. If not, then I have no idea what I'm doing. Caleb -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: gedit2 (Re: CVS rename for nautilussvn)
2012/5/7 Elan Ruusamäe g...@pld-linux.org: 1. rename gedit dir to gedit0 in cvs server side and optionally drop it client side 2. rename gedit2 dir to gedit in cvs server side, and adjust names in files on cvs client side This sounds good. If somebody takes care of the server side bit I'll help cleanup the resulting spec. ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: gedit2 (Re: CVS rename for nautilussvn)
On 07.05.2012 16:14, Caleb Maclennan wrote: 2012/5/7 Elan Ruusamäeg...@pld-linux.org: 1. rename gedit dir to gedit0 in cvs server side and optionally drop it client side 2. rename gedit2 dir to gedit in cvs server side, and adjust names in files on cvs client side This sounds good. If somebody takes care of the server side bit I'll help cleanup the resulting spec. renamed gedit to gedit0 renamed gedit2 to gedit (just in case made backup of gedit2 dir, if somebody wakes up and finds original gedit2 should be kept in cvs as well for some reason) -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
gedit2 (Re: CVS rename for nautilussvn)
On 05/05/12 12:48, Caleb Maclennan wrote: Package copied/renamed server-side. Thank you! Can I ask why our gedit module is called gedit2 on cvs? The upstream project seems to be at 3.4.1, which is what we have in that spec file. Is there any point in keeping that legacy name in our cvs module? probably at some point it was wanted to keep gedit and gedit2 in distro. right now gedit.spec last updated in 2007, and no longer on ftp (even ac) so, feel free to merge gedit2.spec to gedit.spec (and drop the former), just remember to handle obsoletes properly -- 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 rename for nautilussvn
Package copied/renamed server-side. Thank you! Can I ask why our gedit module is called gedit2 on cvs? The upstream project seems to be at 3.4.1, which is what we have in that spec file. Is there any point in keeping that legacy name in our cvs module? Caleb ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: CVS rename for nautilussvn
On Fri, 04 May 2012, Caleb Maclennan wrote: The upstream project NautilusSVN has been renamed to RabbitVCS. Can we get our CVS module renamed or should I work on a new spec? Package copied/renamed server-side. cvs co packages/rabbitvcs You can cvs rm the old package. -- Jan Rękorajski | PLD/Linux SysAdm | http://www.pld-linux.org/ bagginsatmimuw.edu.pl bagginsatpld-linux.org ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
