Re: how to name a prerelease package

1999-07-28 Thread Mark Brown
On Tue, Jul 27, 1999 at 07:26:04PM +, David Coe wrote: > So I don't want to replace the current ispell with it, > until it has been released, but do want to package it and > make it available to users who want to try it (and help > test/debug it). This sounds like experimental (see the new ma

Re: how to name a prerelease package

1999-07-27 Thread Sean 'Shaleh' Perry
> > Maybe a private site is the answer, if cluttering the > ftp space is a concern. > Many of us do now. With apt it is easy. Just put it on va or master if you have no place otherwise. The problem with uploading it is that when it is no longer a "prerelease" you have to get the ftp admins to

Re: how to name a prerelease package

1999-07-27 Thread David Coe
Good questions. The upstream pre-release is beta-quality, "not ready to release, but it's usable" according to the upstream author (words to that effect). So I don't want to replace the current ispell with it, until it has been released, but do want to package it and make it available to users wh

RE: how to name a prerelease package

1999-07-27 Thread Sean 'Shaleh' Perry
On 27-Jul-99 David Coe wrote: > I'm preparing a new distribution of ispell (current upstream > version, just packaging and debian standards changes), and > at the same time preparing to package a prerelease of the > next upstream version. > > Do we have a "standard" or traditional way of nami