I want to move 'contrib' directory up a level

I want to move 'contrib' directory up a level

[Jason Molenda]

In a gnats release/snapshot, there is the top-level directory
(e.g. ``gnats-3.112.1''), below that is a gnats subdirectory (``gnats''),
and below that is the contrib directory with contributed front-ends like
gnatsweb and tkgnats.

I want to move this contrib directory up a level.  Its presence in the
gnats subdir is a reflection on gnats' history as a Cygnus internal
development project; now that it is a project on its own, there is no
reason to keep that baggage.  I think it will be more obvious for users
to see files organized like

  gnats-3.112.1/gnats
  gnats-3.112.1/send-pr
  gnats-3.112.1/contrib


If no one speaks up, I will do it later this week.  Unfortunately,
cvs does not revision control files or directories, so when I do this
everyone will need to do a "cvs update -d" to update their repositories.
If you check out an old branch (e.g. gnats-3.110) from CVS, the contrib
directory will be in its new location, not its old one as you'd expect.


Jason

Re: I want to move 'contrib' directory up a level

[Rick Macdonald]

On Tue, 26 Oct 1999, Jason Molenda wrote:

> I want to move this contrib directory up a level.  Its presence in the
> gnats subdir is a reflection on gnats' history as a Cygnus internal
> development project; now that it is a project on its own, there is no
> reason to keep that baggage.  I think it will be more obvious for users
> to see files organized like
> 
>   gnats-3.112.1/gnats
>   gnats-3.112.1/send-pr
>   gnats-3.112.1/contrib

Fine with me.

Did you get my humble request to include tkgnats-3.0.14 in this release?
Hopefully this is the last 3.x release, so it should have the latest stuff
in contrib.

http://www.cuug.ab.ca/~macdonal/tkgnats/tkgnats-3.0.14.tar.gz

...RickM...

Re: I want to move 'contrib' directory up a level

[Tim Riker]

The contrib stuff quickly is outdated. I would much rather see a simple
document for each contrib package listing the basic info like web site,
ftp address, mailing lists, cvs access, etc. This will avoid the
current:

DL the gnats tarball, including tkgnats, gnatsweb, etc.
DL the updated tkgnats tar ball ...
DL the updated gnatsweb tarball ...

And for packagers such as myself who build RPMs of these there is no
good reason for the gnats RPM to contain tkgnats, as the tkgnats RPM is
newer anyway.

Please consider removing all contrib except docs listing them from the
gnats tar ball.

Rick Macdonald wrote:
> 
> On Tue, 26 Oct 1999, Jason Molenda wrote:
> 
> > I want to move this contrib directory up a level.  Its presence in the
> > gnats subdir is a reflection on gnats' history as a Cygnus internal
> > development project; now that it is a project on its own, there is no
> > reason to keep that baggage.  I think it will be more obvious for users
> > to see files organized like
> >
> >   gnats-3.112.1/gnats
> >   gnats-3.112.1/send-pr
> >   gnats-3.112.1/contrib
> 
> Fine with me.
> 
> Did you get my humble request to include tkgnats-3.0.14 in this release?
> Hopefully this is the last 3.x release, so it should have the latest stuff
> in contrib.
> 
> http://www.cuug.ab.ca/~macdonal/tkgnats/tkgnats-3.0.14.tar.gz
> 
> ...RickM...

-- 
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.

Re: I want to move 'contrib' directory up a level

[Rick Macdonald]

On Tue, 26 Oct 1999, Tim Riker wrote:

> The contrib stuff quickly is outdated. I would much rather see a simple
> document for each contrib package listing the basic info like web site,
> ftp address, mailing lists, cvs access, etc. This will avoid the
> current:
> 
> DL the gnats tarball, including tkgnats, gnatsweb, etc.
> DL the updated tkgnats tar ball ...
> DL the updated gnatsweb tarball ...
> 
> And for packagers such as myself who build RPMs of these there is no
> good reason for the gnats RPM to contain tkgnats, as the tkgnats RPM is
> newer anyway.
> 
> Please consider removing all contrib except docs listing them from the
> gnats tar ball.

Some people want them, some don't. The number of _packagers_ is small
compared to the number of people who grab the gnats tarball. If the
contribs are there, people can try them and then go grab the latest
version of the one(s) they end up using. I vote to keep the contrib as is.

...RickM...

Re: I want to move 'contrib' directory up a level

[Paul Traina]

I actually think tkgnats is mature enough as-is to stand on its own.
I think it's reasonable to place documentation in the contrib area
advertising and suggesting the use of tkgnats,  but it tends to
evolve and improve at a different pace than gnats,  so it makes
sense to break 'em apart.


On Tue, Oct 26, 1999 at 01:22:12PM -0600, Rick Macdonald wrote:
> On Tue, 26 Oct 1999, Tim Riker wrote:
> 
> > The contrib stuff quickly is outdated. I would much rather see a simple
> > document for each contrib package listing the basic info like web site,
> > ftp address, mailing lists, cvs access, etc. This will avoid the
> > current:
> > 
> > DL the gnats tarball, including tkgnats, gnatsweb, etc.
> > DL the updated tkgnats tar ball ...
> > DL the updated gnatsweb tarball ...
> > 
> > And for packagers such as myself who build RPMs of these there is no
> > good reason for the gnats RPM to contain tkgnats, as the tkgnats RPM is
> > newer anyway.
> > 
> > Please consider removing all contrib except docs listing them from the
> > gnats tar ball.
> 
> Some people want them, some don't. The number of _packagers_ is small
> compared to the number of people who grab the gnats tarball. If the
> contribs are there, people can try them and then go grab the latest
> version of the one(s) they end up using. I vote to keep the contrib as is.
> 
> ...RickM...
> 

-- 
Evolution?  I know it's true from personal experience.  I used to be a
butterfly.