[Top][All Lists]

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

Re: [Bug-gnulib] gnulib-tool --import

From: Paul Eggert
Subject: Re: [Bug-gnulib] gnulib-tool --import
Date: 17 Sep 2003 21:04:45 -0700
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

Bruno Haible <address@hidden> writes:

> Where are these two lists stored?

I'd say a separate file.  But it is a tricky question.

> In packages using CVS, should this information go into the CVS?

Shouldn't this depend on the package maintainer?  Some people prefer
"cvs checkout" to yield a tree where "configure; make" works.  Others
prefer a more-minimal CVS checkout, and have an earlier "bootstrap"
shell script.  Surely the latter folks won't want this information in
CVS, since it will be regenerated by "bootstrap".  But the former
folks will probably want it in CVS.

> Is it therefore appropriate to put it into configure.ac?

Perhaps yes, for the plain "configure; make" style.
But surely not, for the "bootstrap; configure; make" style.

> # >>> gnulib module alloca.
> [Here comes the Makefile.am snippet for module 'alloca'.]
> # <<< gnulib module alloca.

A style nit: can you please use a different notation for that?  That
notation conflicts with the notation used by 'cvs update' when there's
a collision.  Visually, unless one is used to non-English quote marks,
the usual parenthesization would be "<<<" ">>>" rather than ">>>"

Simplest would be to reverse the direction of the angle brackets; or
you could substitute "# (((" and "# )))", if you want the notations to
be noticeably different from "cvs update".

reply via email to

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