Re: RFC/ITP: everybuddy-cvs

2000-09-09 Thread Ben Collins
On Fri, Sep 08, 2000 at 11:18:54PM +0200, "J?rgen A. Erhard" wrote: > > "Ben" == Ben Collins <[EMAIL PROTECTED]> writes: > > Ben> On Fri, Sep 01, 2000 at 04:06:33PM +, michael d. ivey wrote: > >> I started making personal debs of the everybuddy CVS snapshots because > EB > >>

Re: RFC/ITP: everybuddy-cvs

2000-09-09 Thread "Jürgen A. Erhard"
> "Ben" == Ben Collins <[EMAIL PROTECTED]> writes: Ben> On Fri, Sep 01, 2000 at 04:06:33PM +, michael d. ivey wrote: >> I started making personal debs of the everybuddy CVS snapshots because EB >> releases tend to lag pretty far behind the code in CVS. I called my >> packa

Re: RFC/ITP: everybuddy-cvs

2000-09-01 Thread Ben Pfaff
"michael d. ivey" <[EMAIL PROTECTED]> writes: > I started making personal debs of the everybuddy CVS snapshots because EB > releases tend to lag pretty far behind the code in CVS. I called my > package ebsnap, and made it conflict with everybuddy. I put it on my > site, and that was that. > > N

Re: RFC/ITP: everybuddy-cvs

2000-09-01 Thread michael d. ivey
On Fri, Sep 01, 2000 at 06:24:55PM +0200, Peter Makholm wrote: > People using unofficial packages should be aware about the > dificulties. So I wouldn't mention the unofficial packages in control > files for official Debian packages. OK. I'll mention it on the website for the unofficial ones. >

Re: RFC/ITP: everybuddy-cvs

2000-09-01 Thread Ben Collins
On Fri, Sep 01, 2000 at 04:06:33PM +, michael d. ivey wrote: > I started making personal debs of the everybuddy CVS snapshots because EB > releases tend to lag pretty far behind the code in CVS. I called my > package ebsnap, and made it conflict with everybuddy. I put it on my > site, and tha

Re: RFC/ITP: everybuddy-cvs

2000-09-01 Thread Peter Makholm
"michael d. ivey" <[EMAIL PROTECTED]> writes: > My current idea is everybuddy-cvs, and make it conflict with everybuddy, > and conflict/replace ebsnap, for the people who may have downloaded > ebsnap. Is that the correct way to proceed? People using unofficial packages should be aware about the

RFC/ITP: everybuddy-cvs

2000-09-01 Thread michael d. ivey
I started making personal debs of the everybuddy CVS snapshots because EB releases tend to lag pretty far behind the code in CVS. I called my package ebsnap, and made it conflict with everybuddy. I put it on my site, and that was that. Now, I've adopted everybuddy and gotten through the NM proce