Re: managing my packages with svn

[Michael Koch]

On Thu, Oct 13, 2005 at 04:57:46PM +0200, Daniel Leidert wrote:
> Am Donnerstag, den 13.10.2005, 15:32 +0300 schrieb Damyan Ivanov:
> > Daniel Leidert wrote:
> > > Am Donnerstag, den 13.10.2005, 11:59 +0200 schrieb Bastian Venthur:
> > >>Does anything speak against my method? BTW: how do I make pdebuild and
> > >>debuild to ignore the .svn dirs?
> > > 
> > > Make an export, not a checkout. But normally debuild/pdebuild should not
> > 
> > Explicit export is not necessary. Use -i argument for debuild.
> 
> I cannot find such an option for debuild, but for dpkg-buildpackage,
> where it is followed by a regex-pattern. Do you really mean this option?

Read the description of it. Without regexp it ignores files of most
common revision control systems.


Cheers,
Michael
-- 
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html

Join the community at http://planet.classpath.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: managing my packages with svn

[Daniel Leidert]

Am Donnerstag, den 13.10.2005, 15:32 +0300 schrieb Damyan Ivanov:
> Daniel Leidert wrote:
> > Am Donnerstag, den 13.10.2005, 11:59 +0200 schrieb Bastian Venthur:
> >>Does anything speak against my method? BTW: how do I make pdebuild and
> >>debuild to ignore the .svn dirs?
> > 
> > Make an export, not a checkout. But normally debuild/pdebuild should not
> 
> Explicit export is not necessary. Use -i argument for debuild.

I cannot find such an option for debuild, but for dpkg-buildpackage,
where it is followed by a regex-pattern. Do you really mean this option?

> Use pdebuild  --- --debbuildopts -i
> or put DEBBUILDOPTS="-i" in /etc/pbuilderrc for pbuilder/pdebuild.
>
> > complain about .svn dirs. Do you mean linda/lintian? In this case, you
> > need to add a short ignore-warning hint for linda/lintian.
> 
> I strongly advice against this. linda/lintian warnings about revision-control
> files in source are there for purpose. Ignorimg them "for convenience" leads 
> to
> uploading source packages with .svn in them.

I am sorry. It was not my intention to say, that it is ok to ignore
these warnings - therefor I also tried to give the hint about export. It
was only the advice, that it can be only ignored with a special file.

Regards, Daniel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: managing my packages with svn

[Damyan Ivanov]

Daniel Leidert wrote:
> Am Donnerstag, den 13.10.2005, 11:59 +0200 schrieb Bastian Venthur:
>>Does anything speak against my method? BTW: how do I make pdebuild and
>>debuild to ignore the .svn dirs?
> 
> Make an export, not a checkout. But normally debuild/pdebuild should not

Explicit export is not necessary. Use -i argument for debuild.
Use pdebuild  --- --debbuildopts -i
or put DEBBUILDOPTS="-i" in /etc/pbuilderrc for pbuilder/pdebuild.

> complain about .svn dirs. Do you mean linda/lintian? In this case, you
> need to add a short ignore-warning hint for linda/lintian.

I strongly advice against this. linda/lintian warnings about revision-control
files in source are there for purpose. Ignorimg them "for convenience" leads to
uploading source packages with .svn in them.

> BTW: I
> suggest to use
> 
> DEBUILD_LINTIAN=yes
> DEBUILD_LINDA=yes
> DEBUILD_LINTIAN_OPTS="-i -I"
> DEBUILD_LINDA_OPTS="-i"
> 
> in /etc/devscripts.conf (runs linda and lintian automatically after
> every debuild run and it further outputs some more info).

Seconded.


dam
-- 
Damyan Ivanov  Creditreform Bulgaria
[EMAIL PROTECTED]  http://www.creditreform.bg/
phone: +359(2)928-2611, 929-3993fax: +359(2)920-0994
mob. +359(88)856-6067   [EMAIL PROTECTED]/Gaim


signature.asc
Description: OpenPGP digital signature

Re: managing my packages with svn

[Damyan Ivanov]

Roberto C. Sanchez wrote:
> Quoting Damyan Ivanov <[EMAIL PROTECTED]>:
> 
>> While dropping dpatch is unthinkable for me (it helps a great deal when
>> reviewing diff.gz for unwanted changes), documenting its usage in
>> README.Debian
>> is indeed a very good idea.
> 
> Except that README.Debian is not the place for something like that. 
> Only things
> relevant to the *user* of the package should go there.  Things like what
> build
> system are used or what additional development tools are user belong in
> another
> README that can be put only in the source package but not the binary
> package.

I agree. In fact the README in question is named debian/README.dpatch and is
not included in any binary packages. Just as you suggested.


dam
-- 
Damyan Ivanov  Creditreform Bulgaria
[EMAIL PROTECTED]  http://www.creditreform.bg/
phone: +359(2)928-2611, 929-3993fax: +359(2)920-0994
mob. +359(88)856-6067   [EMAIL PROTECTED]/Gaim


signature.asc
Description: OpenPGP digital signature

Re: managing my packages with svn

[Roberto C. Sanchez]

Quoting Damyan Ivanov <[EMAIL PROTECTED]>:



While dropping dpatch is unthinkable for me (it helps a great deal when
reviewing diff.gz for unwanted changes), documenting its usage in 
README.Debian

is indeed a very good idea.



Except that README.Debian is not the place for something like that.  
Only things

relevant to the *user* of the package should go there.  Things like what build
system are used or what additional development tools are user belong in 
another

README that can be put only in the source package but not the binary package.

-Roberto

--
Roberto C. Sanchez
http://familiasanchez.net/~roberto


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: managing my packages with svn

[Daniel Leidert]

Am Donnerstag, den 13.10.2005, 11:59 +0200 schrieb Bastian Venthur:
> Fathi Boudra wrote:
> 
> > Le Jeudi 13 Octobre 2005 10:53, Bastian Venthur a écrit :
> >> Hi mentors,
> >> In order to keep track of my changes in the development of my packages
> >> I've decided to put my "debian" folder with all the packages and sources
> >> inside into a svn repo.
> >>
> >> My question is simple: Are there common pitfalls I should look out for? I
> >> could imagine, that all the new .svn dirs in every folder could cause
> >> some trouble, when building new packages.
> > 
> > take a look at http://workaround.org/moin/SvnBuildpackage
> 
> Thanks for pointing me to SvnBuildpackage. Allthough I think it provides a
> good way of keeping track of your changes, I'm afraid the whole
> buildprocess becomes too complicated -- especially for New Maintainers (me
> included).

I don't use/know svn-buildpackage, but cvs-buildpackage and I can tell
you, it is very easy to use (so I think, svn-buildpackage is too if you
know svn).

> I think I still prefer the easy way by just putting the debian-dir (where
> all my packages are stored) under svn control or maybe an own repo for
> every package.

If you want to have a look at a cvs-repo for Debian packages have a look
at http://cvs.wgdd.de/cgi-bin/cvsweb/?cvsroot=debian. So if you want,
you can also test cvs-buildpackage with anonymous checkout. If you
really want to give it a try, I suggest to use "cvs-buildpackage
-C'debuild ...'".

> This way I just have to deal with two seperate problems:
> (1) ci/co
> (2) building the package as usual
> 
> Does anything speak against my method? BTW: how do I make pdebuild and
> debuild to ignore the .svn dirs?

Make an export, not a checkout. But normally debuild/pdebuild should not
complain about .svn dirs. Do you mean linda/lintian? In this case, you
need to add a short ignore-warning hint for linda/lintian. BTW: I
suggest to use

DEBUILD_LINTIAN=yes
DEBUILD_LINDA=yes
DEBUILD_LINTIAN_OPTS="-i -I"
DEBUILD_LINDA_OPTS="-i"

in /etc/devscripts.conf (runs linda and lintian automatically after
every debuild run and it further outputs some more info).

just my 2 cents
Regards, Daniel

Re: managing my packages with svn

[Damyan Ivanov]

Bastian Venthur wrote:
> BTW: how do I make pdebuild and
> debuild to ignore the .svn dirs?

`debuild -i' works for sure. It passes all short options to build-package.
Don't know about pdebuild.


dam
-- 
Damyan Ivanov  Creditreform Bulgaria
[EMAIL PROTECTED]  http://www.creditreform.bg/
phone: +359(2)928-2611, 929-3993fax: +359(2)920-0994
mob. +359(88)856-6067   [EMAIL PROTECTED]/Gaim


signature.asc
Description: OpenPGP digital signature

Re: managing my packages with svn

[Fathi BOUDRA]

> BTW: how do I make pdebuild and
> debuild to ignore the .svn dirs?

instead checkout, use export. it gives you an arbo. without the svn dirs.

cheers,

Fathi


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: managing my packages with svn

[Bastian Venthur]

Fathi Boudra wrote:

> Le Jeudi 13 Octobre 2005 10:53, Bastian Venthur a écrit :
>> Hi mentors,
>> In order to keep track of my changes in the development of my packages
>> I've decided to put my "debian" folder with all the packages and sources
>> inside into a svn repo.
>>
>> My question is simple: Are there common pitfalls I should look out for? I
>> could imagine, that all the new .svn dirs in every folder could cause
>> some trouble, when building new packages.
> 
> take a look at http://workaround.org/moin/SvnBuildpackage

Thanks for pointing me to SvnBuildpackage. Allthough I think it provides a
good way of keeping track of your changes, I'm afraid the whole
buildprocess becomes too complicated -- especially for New Maintainers (me
included).

I think I still prefer the easy way by just putting the debian-dir (where
all my packages are stored) under svn control or maybe an own repo for
every package.

This way I just have to deal with two seperate problems:
(1) ci/co
(2) building the package as usual

Does anything speak against my method? BTW: how do I make pdebuild and
debuild to ignore the .svn dirs?



Kind regards

Bastian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: managing my packages with svn

[Damyan Ivanov]

Florian Ernst wrote:
> Hello *,
> 
> On Thu, Oct 13, 2005 at 12:04:24PM +0300, Damyan Ivanov wrote:
> 
>>No need to put all sources in the repo, though. Use dpatch or something like 
>>it
> 
>   
> ^^^
>>and you'll have to put only debian/ under revision control, since the rest 
>>will
>>never change :-)
> 
> While this might be considered an advantage there's a downside
> connected with it, see for example the blog entry
> "dpatch/dbs/etc/etc/etc/etc considered harmful" from Joey Hess at
> .

While dropping dpatch is unthinkable for me (it helps a great deal when
reviewing diff.gz for unwanted changes), documenting its usage in README.Debian
is indeed a very good idea.

Thanks,
dam
-- 
Damyan Ivanov  Creditreform Bulgaria
[EMAIL PROTECTED]  http://www.creditreform.bg/
phone: +359(2)928-2611, 929-3993fax: +359(2)920-0994
mob. +359(88)856-6067   [EMAIL PROTECTED]/Gaim


signature.asc
Description: OpenPGP digital signature

Re: managing my packages with svn

[Fathi Boudra]

Le Jeudi 13 Octobre 2005 10:53, Bastian Venthur a écrit :
> Hi mentors,
> In order to keep track of my changes in the development of my packages I've
> decided to put my "debian" folder with all the packages and sources inside
> into a svn repo.
>
> My question is simple: Are there common pitfalls I should look out for? I
> could imagine, that all the new .svn dirs in every folder could cause some
> trouble, when building new packages.

take a look at http://workaround.org/moin/SvnBuildpackage

cheers

Fathi

Re: managing my packages with svn

[Florian Ernst]

Hello *,

On Thu, Oct 13, 2005 at 12:04:24PM +0300, Damyan Ivanov wrote:
> No need to put all sources in the repo, though. Use dpatch or something like 
> it
  
^^^
> and you'll have to put only debian/ under revision control, since the rest 
> will
> never change :-)

While this might be considered an advantage there's a downside
connected with it, see for example the blog entry
"dpatch/dbs/etc/etc/etc/etc considered harmful" from Joey Hess at
.

Cheers,
Flo


signature.asc
Description: Digital signature

Re: managing my packages with svn

[Florian Ernst]

Hello *,

On Thu, Oct 13, 2005 at 10:53:29AM +0200, Bastian Venthur wrote:
> In order to keep track of my changes in the development of my packages I've
> decided to put my "debian" folder with all the packages and sources inside
> into a svn repo.
> 
> My question is simple: Are there common pitfalls I should look out for? I
> could imagine, that all the new .svn dirs in every folder could cause some
> trouble, when building new packages.

Adding to what Damyan already mentioned the documentation found in the
package "svn-buildpackage" might be worth investigating if you want to
use svn.

Cheers,
Flo


signature.asc
Description: Digital signature

Re: managing my packages with svn

[Damyan Ivanov]

Bastian Venthur wrote:
> Hi mentors,
> In order to keep track of my changes in the development of my packages I've
> decided to put my "debian" folder with all the packages and sources inside
> into a svn repo.

Good.

No need to put all sources in the repo, though. Use dpatch or something like it
and you'll have to put only debian/ under revision control, since the rest will
never change :-)

> My question is simple: Are there common pitfalls I should look out for? I
> could imagine, that all the new .svn dirs in every folder could cause some
> trouble, when building new packages.

Just use the -i option when building your packages and dpkg-source will happily
ignore .svn, CVS (and maybe others) directories.


dam
-- 
Damyan Ivanov  Creditreform Bulgaria
[EMAIL PROTECTED]  http://www.creditreform.bg/
phone: +359(2)928-2611, 929-3993fax: +359(2)920-0994
mob. +359(88)856-6067   [EMAIL PROTECTED]/Gaim


signature.asc
Description: OpenPGP digital signature

managing my packages with svn

[Bastian Venthur]

Hi mentors,
In order to keep track of my changes in the development of my packages I've
decided to put my "debian" folder with all the packages and sources inside
into a svn repo.

My question is simple: Are there common pitfalls I should look out for? I
could imagine, that all the new .svn dirs in every folder could cause some
trouble, when building new packages.


Kind regards

Bastian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]