Re: RFC: quilt-el

2006-07-05 Thread Adeodato Simó
* Jari Aalto+mail.linux [Mon, 03 Jul 2006 23:30:55 +0300]: > I wouldn't use quilt alone, because it is stack based and I mostly try > to make all patches completely separate from each other. This is nonsense. Either two patches touch the same group of lines in a file, or they don't, period. If t

Re: RFC: quilt-el

2006-07-03 Thread Jari Aalto+mail.linux
* Mon 2006-07-03 Frank Küster * Message-Id: 86bqs6h0k2.fsf AT alhambra.kuesterei.ch > [EMAIL PROTECTED] (Jari Aalto+mail.linux) wrote: >> I have found that the duo works best this way: >> >> - init quilt >> - make changes under quilt supervisions >> - when satisfied, convert to dpatch >> >> [ rep

Re: RFC: quilt-el

2006-07-03 Thread Frank Küster
[EMAIL PROTECTED] (Jari Aalto+mail.linux) wrote: > * Mon 2006-07-03 Yavor Doganov > * Message-Id: pan.2006.07.03.09.01.44.129385 AT doganov.org >> On Sun, 02 Jul 2006 20:41:12 +0300, Jari Aalto+mail.linux wrote: >> >>> Use 3. When the upstream releases new version you can drop the patches. >>> Us

Re: RFC: quilt-el

2006-07-03 Thread Jari Aalto+mail.linux
* Mon 2006-07-03 Yavor Doganov * Message-Id: pan.2006.07.03.09.01.44.129385 AT doganov.org > On Sun, 02 Jul 2006 20:41:12 +0300, Jari Aalto+mail.linux wrote: > >> Use 3. When the upstream releases new version you can drop the patches. >> Using dpatch(1) to manage this is easy > > Given the name of

Re: RFC: quilt-el

2006-07-03 Thread Yavor Doganov
On Sun, 02 Jul 2006 20:41:12 +0300, Jari Aalto+mail.linux wrote: > Use 3. When the upstream releases new version you can drop the patches. > Using dpatch(1) to manage this is easy Given the name of the package in question, I don't really think that he'd be using dpatch ;-} -- JID: [EMAIL PROTEC

Re: RFC: quilt-el

2006-07-02 Thread Adeodato Simó
* Satoru Takeuchi [Sun, 02 Jul 2006 23:18:39 +0900]: > 1. package stable release version > 2. package developing version and don't apply any extra patches > 3. package developing version and apply bug fix patch > 4. wait for upstream to apply bug fix patch and release stable release > 5. something

Re: RFC: quilt-el

2006-07-02 Thread Jari Aalto+mail.linux
* Sun 2006-07-02 Satoru Takeuchi * Message-Id: 87d5coks3k.wl%nqm08501 AT nifty.com > Hi mentors, > > I'd like to package quilt-el and submitted ITP[1] about two months ago. > > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364611 > > Now I have a problem with it. I can't decide which versio

Re: RFC: quilt-el

2006-07-02 Thread Benjamin Mesing
On Sun, 2006-07-02 at 16:28 +0200, Soren Hansen wrote: > On Sun, Jul 02, 2006 at 11:18:39PM +0900, Satoru Takeuchi wrote: > > 1. package stable release version > > 2. package developing version and don't apply any extra patches > > 3. package developing version and apply bug fix patch > > 4. wait

Re: RFC: quilt-el

2006-07-02 Thread Soren Hansen
On Sun, Jul 02, 2006 at 11:18:39PM +0900, Satoru Takeuchi wrote: > 1. package stable release version > 2. package developing version and don't apply any extra patches > 3. package developing version and apply bug fix patch > 4. wait for upstream to apply bug fix patch and release stable release >

RFC: quilt-el

2006-07-02 Thread Satoru Takeuchi
Hi mentors, I'd like to package quilt-el and submitted ITP[1] about two months ago. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364611 Now I have a problem with it. I can't decide which version I should package. Firstly, its stable release version[2] is quite old and has many bugs. Seco