Re: File names (and synchronization)

[Bastiaan Veelo]

Peter Simons wrote:

> Bastiaan Veelo writes:
>
> > I see two reasons why we may want to rename files now:
>
> > 1) complyance with policy point 3
> > (http://www.gnu.org/software/ac-archive/policy.html)
>
> You realize that just renaming the file won't suffice,
> right? Someone would have to edit the macros too. I wouldn't
> want to keep a macro called AC_FOO in a file called
> ax_foo.m4.
>  

Yes, and the old file should have an obsolete notice with a pointer to 
the new macro. I just figured that if this is the policy, you probably 
want as many files as possible to comply with it, so this may be the 
time. Apropos, is there a neat way to let autoconf complain when it is 
attempted to be run on an obsoleted macro?

> About synchronization: Wouldn't it be beneficial if Guido's
> archive would generate its presentation from the _same_ CVS
> repository as gnu.org does? The problem I see right now is
> that there are still numerous macros in the sf.net
> repository that are _not_ on gnu.org, and I don't see any
> technical reason why that would be. Guido, what do you
> think? Could we agree to _both_ use the repository on
> Savannah? And to commit new entries there and only there?
>  

I think this would be beneficial.

Regards,
Bastiaan.