On Sat, Aug 30, 2003 at 12:33:29AM +0200, Eduard Bloch wrote:
> #include
> * Jamin W. Collins [Fri, Aug 29 2003, 03:13:44PM]:
>
> > What _stupidness_ are you refering to? I've always just used something
> > like:
> >
> >svn merge http://pkg/upstream/a.b http://pkg/upstream/current trunk
>
Eduard Bloch wrote:
> However, a possible implementation failed completely because of
> stupideness of "svn merge". So we have to find an alternative solution
> with diff&patch&cp. OTOH it is not possible to keep the version history of
> every file.
I think you're looking for svn_load_dirs.
--
s
#include
* Jamin W. Collins [Fri, Aug 29 2003, 03:13:44PM]:
> What _stupidness_ are you refering to? I've always just used something
> like:
>
>svn merge http://pkg/upstream/a.b http://pkg/upstream/current trunk
Always? Nice to see that it can work with three arguments and apply the
change
On Fri, Aug 29, 2003 at 10:30:46PM +0200, Eduard Bloch wrote:
>
> Question: how do you manage upstream and Debian branches? I encounter
> this problem while trying to find the best concept for svn-uupdate.
>
> The first idea was:
>
> branches/upstream/a.b ---> branches/ups
#include
* Joey Hess [Fri, Aug 29 2003, 12:35:46PM]:
> Actually, dpkg-buildpackage does not care what you name the build
> directory of a package.
>
> Persaonally, I use just packagename for the directory names and build
> directly from them, using a collection of ugly hacks to ignore the .svn
>
Eduard Bloch wrote:
> However, a possible implementation failed completely because of
> stupideness of "svn merge". So we have to find an alternative solution
> with diff&patch&cp. OTOH it is not possible to keep the version history of
> every file.
I think you're looking for svn_load_dirs.
--
s
#include
* Jamin W. Collins [Fri, Aug 29 2003, 03:13:44PM]:
> What _stupidness_ are you refering to? I've always just used something
> like:
>
>svn merge http://pkg/upstream/a.b http://pkg/upstream/current trunk
Always? Nice to see that it can work with three arguments and apply the
change
On Sat, Aug 30, 2003 at 12:33:29AM +0200, Eduard Bloch wrote:
> #include
> * Jamin W. Collins [Fri, Aug 29 2003, 03:13:44PM]:
>
> > What _stupidness_ are you refering to? I've always just used something
> > like:
> >
> >svn merge http://pkg/upstream/a.b http://pkg/upstream/current trunk
>
On Fri, Aug 29, 2003 at 12:30:46PM -0400, Joey Hess wrote:
> Fabian Fagerholm wrote:
> > * B.B. svn_load_dirs -t tags/projectX/upstream/
> >url://host/repos/ branches/projectX/upstream
> >/path/to/new/version
>
> I've only ever had to do this once, and
Jamin W. Collins wrote:
> I was with you up to this point. I don't normally name my working copy
> in the form project- as that form is needed for actually making
> hte package and for that we need an exported copy of the working copy.
Actually, dpkg-buildpackage does not care what you name the b
Fabian Fagerholm wrote:
> Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
> insight into this issue. I will try to summarize everything in this
> reply to myself.
Nice job writing this up, here are some corrections.
> The repository will have the following structure:
>
> trun
#include
* Joey Hess [Fri, Aug 29 2003, 12:35:46PM]:
> Actually, dpkg-buildpackage does not care what you name the build
> directory of a package.
>
> Persaonally, I use just packagename for the directory names and build
> directly from them, using a collection of ugly hacks to ignore the .svn
>
On Fri, Aug 29, 2003 at 10:30:46PM +0200, Eduard Bloch wrote:
>
> Question: how do you manage upstream and Debian branches? I encounter
> this problem while trying to find the best concept for svn-uupdate.
>
> The first idea was:
>
> branches/upstream/a.b ---> branches/ups
#include
* Fabian Fagerholm [Fri, Aug 29 2003, 12:44:02PM]:
> On Thu, 2003-08-28 at 22:24, Fabian Fagerholm wrote:
> > How do I manage a new Debian package with Subversion?
>
> Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
> insight into this issue. I will try to summarize everythin
On Fri, Aug 29, 2003 at 12:44:02PM +0300, Fabian Fagerholm wrote:
>
> * Check out the trunk you just created into a directory called
> project- (svn co).
I was with you up to this point. I don't normally name my working copy
in the form project- as that form is needed for actually m
On Thu, Aug 28, 2003 at 10:24:57PM +0300, Fabian Fagerholm wrote:
>
> How do I manage a new Debian package with Subversion?
>
> The things I've found only scratch the surface a bit, assume a level
> of knowledge beyond mine, or assume you're migrating from CVS and
> already have made several init
On Fri, Aug 29, 2003 at 12:30:46PM -0400, Joey Hess wrote:
> Fabian Fagerholm wrote:
> > * B.B. svn_load_dirs -t tags/projectX/upstream/
> >url://host/repos/ branches/projectX/upstream
> >/path/to/new/version
>
> I've only ever had to do this once, and
Jamin W. Collins wrote:
> I was with you up to this point. I don't normally name my working copy
> in the form project- as that form is needed for actually making
> hte package and for that we need an exported copy of the working copy.
Actually, dpkg-buildpackage does not care what you name the b
Fabian Fagerholm wrote:
> Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
> insight into this issue. I will try to summarize everything in this
> reply to myself.
Nice job writing this up, here are some corrections.
> The repository will have the following structure:
>
> trun
#include
* Fabian Fagerholm [Fri, Aug 29 2003, 12:44:02PM]:
> On Thu, 2003-08-28 at 22:24, Fabian Fagerholm wrote:
> > How do I manage a new Debian package with Subversion?
>
> Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
> insight into this issue. I will try to summarize everythin
On Thu, Aug 28, 2003 at 09:56:29PM -0400, Joey Hess wrote:
> Jamin W. Collins wrote:
> > I prefer an alternate structure where you start with the project as
> > a top level. This keeps all project (package) related files under
> > one directory in the project:
> >
> >project/
> > tru
Jamin W. Collins wrote:
> I prefer an alternate structure where you start with the project as a
> top level. This keeps all project (package) related files under one
> directory in the project:
>
>project/
> trunk/
> branches/
> tags/
> vendor/
The only problem wit
On Thu, 2003-08-28 at 22:24, Fabian Fagerholm wrote:
> How do I manage a new Debian package with Subversion?
Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
insight into this issue. I will try to summarize everything in this
reply to myself.
Managing Debian packages wi
On Thu, 2003-08-28 at 22:24, Fabian Fagerholm wrote:
> How do I manage a new Debian package with Subversion?
Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
insight into this issue. I will try to summarize everything in this
reply to myself.
Managing Debian packages wi
On Fri, Aug 29, 2003 at 12:44:02PM +0300, Fabian Fagerholm wrote:
>
> * Check out the trunk you just created into a directory called
> project- (svn co).
I was with you up to this point. I don't normally name my working copy
in the form project- as that form is needed for actually m
On Thu, Aug 28, 2003 at 09:56:29PM -0400, Joey Hess wrote:
> Jamin W. Collins wrote:
> > I prefer an alternate structure where you start with the project as
> > a top level. This keeps all project (package) related files under
> > one directory in the project:
> >
> >project/
> > tru
Jamin W. Collins wrote:
> I prefer an alternate structure where you start with the project as a
> top level. This keeps all project (package) related files under one
> directory in the project:
>
>project/
> trunk/
> branches/
> tags/
> vendor/
The only problem wit
On Thu, Aug 28, 2003 at 02:13:51PM -0600, Jamin W. Collins wrote:
>
> Yes, that way you have a source structure devoid of the .svn
> subdirectories. I use the attached export script to ease the and build
> process. It assumes it is run from the project directory and that the
> orig source file a
On Thu, Aug 28, 2003 at 10:24:57PM +0300, Fabian Fagerholm wrote:
>
> How do I manage a new Debian package with Subversion?
>
> The things I've found only scratch the surface a bit, assume a level
> of knowledge beyond mine, or assume you're migrating from CVS and
> already have made several init
On Thu, Aug 28, 2003 at 02:13:51PM -0600, Jamin W. Collins wrote:
>
> Yes, that way you have a source structure devoid of the .svn
> subdirectories. I use the attached export script to ease the and build
> process. It assumes it is run from the project directory and that the
> orig source file a
30 matches
Mail list logo
