Re: Bits from the GNOME Team
- To: ross@burtonini.com
- Cc: hertzog@debian.org, debian-gtk-gnome@lists.debian.org, jordi@debian.org, joss@debian.org, netsnipe@users.sourceforge.net, kitame@debian.org, emil@nishra.com, j.rohr@comlink.apc.org, ejad@debian.org, kov@debian.org, robster@debian.org, seb128@debian.org, tagoh@debian.org
- Subject: Re: Bits from the GNOME Team
- From: Akira TAGOH <tagoh@debian.org>
- Date: Wed, 24 Sep 2003 21:40:42 +0900 (JST)
- Message-id: <[🔎] 20030924.214042.304121703.tagoh@debian.org>
- In-reply-to: <[🔎] 1064400511.483.90.camel@carados.180sw.com>
- References: <[🔎] 1064398346.483.87.camel@carados.180sw.com> <[🔎] 20030924104701.GA17774@home.ouaza.com> <[🔎] 1064400511.483.90.camel@carados.180sw.com>
>>>>> On Wed, 24 Sep 2003 11:48:31 +0100,
>>>>> "RB" == Ross Burton <ross@burtonini.com> wrote:
RB> Thats a good point. Are there tools to make managing just debian/ in
RB> CVS easy, or should we write some as we go?
I'm assuming the patches isn't applied to the source
directly.
- apt-get source <source package>
- cvs up
- changes the changelog.
- remove the old debian/
- copy the new debian/ (make sure to remove CVS directories)
- build
I think it works well. how about creating Makefile to build
the package and import it to CVS/SVN? and if something can
be shared, Makefile includes the splited common Makefile?
Regards,
--
Akira TAGOH : tagoh@gnome.gr.jp / Japan GNOME Users Group
at@gclab.org : tagoh@gnome-db.org / GNOME-DB Project
: tagoh@redhat.com / Red Hat, Inc.
: tagoh@debian.org / Debian Project
Reply to: