[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FYI: 86-gary-commit-list-posts.patch

From: Scott James Remnant
Subject: Re: FYI: 86-gary-commit-list-posts.patch
Date: Wed, 11 Feb 2004 15:42:40 +0000

On Wed, 2004-02-11 at 08:27, Gary V.Vaughan wrote:

> On 11 Feb 2004, at 02:33, Scott James Remnant wrote:
> > Uh, neither commit nor mail/ have ever, to my knowledge, been in a
> > libtool release...
> >
> > commit isn't in EXTRA_DIST ... can we remove config/mailnotify from
> > there, please
> Playing devils advocate for the moment: maybe we should add our commit 
> script to EXTRA_DIST for the reasons above?
You only need these scripts if you've checked Libtool out from CVS,
they'll only work if there's the appropriate CVS "checked out" metadata
alongside them, so they'd be fairly useless in the release tarball.

> I can see the argument from both sides.  My only concern is 
> consistency; if we do decide to remove our CVS utilities from release 
> tarballs, then bootstrap needs to go too.
There are circumstances where being able to re-bootstrap a Libtool
release can be useful, it only needs the auto*tools installed on the
system to make it possible.

The only circumstances where commit and mailnotify would be useful are
if you've checked Libtool out of CVS, made some changes and want to give
them back (and you've got commit access).  Inside the release tarball,
they're pointless as even we can't run ./commit inside there to commit
the changes.

> My vote:
>      +0.5 for adding commit
Mine -1 for adding commit
     -0.25 for removing bootstrap

Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]