Re: Custom package versioning

2001-04-17 Thread tony mancill
On Tue, 17 Apr 2001, Amaya wrote: > At work, we are making custom Debian packages and we need a special > versioning system so that apt does not try to replace our package with > a newer upstream one. > > I would like to know if there's a standard way to proceed, apart from > setting the debian v

Re: Custom package versioning

2001-04-17 Thread tony mancill
On Tue, 17 Apr 2001, Amaya wrote: > At work, we are making custom Debian packages and we need a special > versioning system so that apt does not try to replace our package with > a newer upstream one. > > I would like to know if there's a standard way to proceed, apart from > setting the debian

Re: Custom package versioning

2001-04-17 Thread Bradley Bell
On Tue, Apr 17, 2001 at 11:18:32AM +0200, Amaya wrote: > Hello all, > > At work, we are making custom Debian packages and we need a special versioning > system so that apt does not try to replace our package with a newer upstream > one. > > I would like to know if there's a standard way to procee

Re: Custom package versioning

2001-04-17 Thread Julian Gilbey
On Tue, Apr 17, 2001 at 11:18:32AM +0200, Amaya wrote: > Hello all, > > At work, we are making custom Debian packages and we need a special versioning > system so that apt does not try to replace our package with a newer upstream > one. > > I would like to know if there's a standard way to procee

Re: Custom package versioning

2001-04-17 Thread Bradley Bell
On Tue, Apr 17, 2001 at 11:18:32AM +0200, Amaya wrote: > Hello all, > > At work, we are making custom Debian packages and we need a special versioning > system so that apt does not try to replace our package with a newer upstream > one. > > I would like to know if there's a standard way to proce

Re: Custom package versioning

2001-04-17 Thread Julian Gilbey
On Tue, Apr 17, 2001 at 11:18:32AM +0200, Amaya wrote: > Hello all, > > At work, we are making custom Debian packages and we need a special versioning > system so that apt does not try to replace our package with a newer upstream > one. > > I would like to know if there's a standard way to proce