From: Graham W. <bo...@de...> - 2004-06-11 23:22:31
|
I would like (if everyone agrees that it is alright) to put the Debian package under version control with the rest of fetchmail at Berlios. This would entail creating a branches/debian directory for the Debian packaging branch. This would keep all Debian related changes specific to this one branch directory. Under the directory would be (for example): $ svn ls svn+ssh://svn.berlios.de/svnroot/repos/fetchmail/branches/debian 6.2.5-9 6.2.6-1 current where current is the current Debian package (unreleased) and the other listings are tags for older Debian packages. Thoughts? -- gram |
From: Matthias A. <mat...@gm...> - 2004-06-11 23:58:47
|
Graham Wilson schrieb am 2004-06-11: > I would like (if everyone agrees that it is alright) to put the Debian > package under version control with the rest of fetchmail at Berlios. > > This would entail creating a branches/debian directory for the Debian > packaging branch. This would keep all Debian related changes specific to > this one branch directory. Under the directory would be (for example): Is the branch a modified fetchmail version or a separate package? If it is separate, the branch may not be the optimal way to formulate what it is. -- Matthias Andree Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 |
From: Graham W. <bo...@de...> - 2004-06-16 00:58:15
|
On Fri, Jun 11, 2004 at 11:58:44PM +0200, Matthias Andree wrote: > Graham Wilson schrieb am 2004-06-11: > > I would like (if everyone agrees that it is alright) to put the Debian > > package under version control with the rest of fetchmail at Berlios. > > > > This would entail creating a branches/debian directory for the Debian > > packaging branch. This would keep all Debian related changes specific to > > this one branch directory. Under the directory would be (for example): > > Is the branch a modified fetchmail version or a separate package? If it > is separate, the branch may not be the optimal way to formulate what it > is. I am not sure what you mean, but I'll describe the current situation and let you guys decide. The current Debian package of fetchmail is a patched version of fetchmail, with the addition of a debian directory in the toplevel of the source. Now, that development has picked up again, I'd like to either merge or drop the Debian-specific patches into the trunk, so that the Debian package only ends up as the trunk plus the debian directory. The reason I'd like to keep this in the same repository as fetchmail is because it would make merging stuff from the Debian package to and from the main fetchmail source easy. This will facilitate me updating the Debian package, as well as me working on merging Debian-specific patches into the trunk. So, what do you guys think? -- gram |
From: Matthias A. <mat...@gm...> - 2004-06-16 02:22:54
|
Graham Wilson schrieb am 2004-06-15: > The current Debian package of fetchmail is a patched version of > fetchmail, with the addition of a debian directory in the toplevel of > the source. Now, that development has picked up again, I'd like to > either merge or drop the Debian-specific patches into the trunk, so > that the Debian package only ends up as the trunk plus the debian > directory. > > The reason I'd like to keep this in the same repository as fetchmail is > because it would make merging stuff from the Debian package to and from > the main fetchmail source easy. This will facilitate me updating the > Debian package, as well as me working on merging Debian-specific patches > into the trunk. > > So, what do you guys think? I don't have general objections - but let's review the patches first :-) I wonder if the Debian directory should also be here if that made sense. -- Matthias Andree Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 |
From: Graham W. <bo...@de...> - 2004-06-16 23:32:57
|
On Wed, Jun 16, 2004 at 02:22:51AM +0200, Matthias Andree wrote: > Graham Wilson schrieb am 2004-06-15: > > The current Debian package of fetchmail is a patched version of > > fetchmail, with the addition of a debian directory in the toplevel > > of the source. Now, that development has picked up again, I'd like > > to either merge or drop the Debian-specific patches into the trunk, > > so that the Debian package only ends up as the trunk plus the debian > > directory. > > > > The reason I'd like to keep this in the same repository as fetchmail > > is because it would make merging stuff from the Debian package to > > and from the main fetchmail source easy. This will facilitate me > > updating the Debian package, as well as me working on merging > > Debian-specific patches into the trunk. > > > > So, what do you guys think? > > I don't have general objections - but let's review the patches first :-) That was my plan. When I import the Debian source tree I can start looking at the differences. > I wonder if the Debian directory should also be here if that made > sense. The general consensus among other developers is that doing so is not a good idea, since fixes only to the Debian directory might require new releases. Also, those downloading the tarball, or checking out a copy from CVS would have a Debian directory that they wouldn't be interested in. Additionally, I might (for some reason or other) need to patch the fetchmail source tree in a way that only affects Debian, and I wouldn't want to have to put the patch in the trunk. -- gram |