On Tue, Feb 13, 2001 at 10:21:59AM +0100, peter karlsson wrote:
> Chad C. Walstrom:
>
> > The easiest way is to maintain a vendor branch in a local repository.
>
> I would prefer not to make unnecessary copies...
In that case, try creating a branch in the upstream CVS module, rather than a
sepa
On Tue, Feb 13, 2001 at 10:21:59AM +0100, peter karlsson wrote:
> Chad C. Walstrom:
>
> > The easiest way is to maintain a vendor branch in a local repository.
>
> I would prefer not to make unnecessary copies...
In that case, try creating a branch in the upstream CVS module, rather than a
sep
peter karlsson wrote:
> I would prefer not to make unnecessary copies...
I think you're referring to the local repository as being unnecessary,
in which case I'd agree with you. However, if you do use local
repositories and do not have direct upstream CVS access, vendor
branchanes are far too con
peter karlsson wrote:
> I would prefer not to make unnecessary copies...
I think you're referring to the local repository as being unnecessary,
in which case I'd agree with you. However, if you do use local
repositories and do not have direct upstream CVS access, vendor
branchanes are far too co
peter karlsson <[EMAIL PROTECTED]> writes:
> Ah. cvs-buildpackage. Yeah, that one could need some documentation. I tried
> using it once, but gave up. And I do have some CVS knowledge... :-)
I've been using it for years. All I have ever done is cut and paste
from the documentation.
jason
--
``
Chad C. Walstrom:
> The easiest way is to maintain a vendor branch in a local repository.
I would prefer not to make unnecessary copies...
> You can use the cvs-inject script provided by cvs-buildpackage to
> automate much of this. (Do an 'apt-cache show cvs-buildpackage'.)
Ah. cvs-buildpackag
peter karlsson <[EMAIL PROTECTED]> writes:
> Ah. cvs-buildpackage. Yeah, that one could need some documentation. I tried
> using it once, but gave up. And I do have some CVS knowledge... :-)
I've been using it for years. All I have ever done is cut and paste
from the documentation.
jason
--
`
Chad C. Walstrom:
> The easiest way is to maintain a vendor branch in a local repository.
I would prefer not to make unnecessary copies...
> You can use the cvs-inject script provided by cvs-buildpackage to
> automate much of this. (Do an 'apt-cache show cvs-buildpackage'.)
Ah. cvs-buildpacka
Regarding: Debian native package v.s. Upstream *.orig.tar.gz + *.diff
Joshua Haberman wrote:
> Really? I was told by someone else that it makes things much more
> complicated, since you have to release a new upstream version for
> any debian-specific changes to be made. I'll refrain from quoting
>
Regarding: Debian native package v.s. Upstream *.orig.tar.gz + *.diff
Joshua Haberman wrote:
> Really? I was told by someone else that it makes things much more
> complicated, since you have to release a new upstream version for
> any debian-specific changes to be made. I'll refrain from quoting
On Mon, Feb 12, 2001 at 09:25:26PM +0100, peter karlsson wrote:
> I have CVS access to a upstream program I am the Debian maintainer for
> (jwhois), and since I have learnt the lesson of moving the debian
> directory in the CVS, I'm planning to add them as a separate module.
>
> My question, howev
Hi!
I have CVS access to a upstream program I am the Debian maintainer for
(jwhois), and since I have learnt the lesson of moving the debian
directory in the CVS, I'm planning to add them as a separate module.
My question, however, is how to handle differences between the Debian
version and the u
On Mon, Feb 12, 2001 at 09:25:26PM +0100, peter karlsson wrote:
> I have CVS access to a upstream program I am the Debian maintainer for
> (jwhois), and since I have learnt the lesson of moving the debian
> directory in the CVS, I'm planning to add them as a separate module.
>
> My question, howe
Hi!
I have CVS access to a upstream program I am the Debian maintainer for
(jwhois), and since I have learnt the lesson of moving the debian
directory in the CVS, I'm planning to add them as a separate module.
My question, however, is how to handle differences between the Debian
version and the
14 matches
Mail list logo
