Re: Conversion to /package

Paul Jarc wrote:
> Dan Kegel <[email protected]> wrote:
> 
>>How about an autoconf macro AC_SLASHPACKAGE which would take the name
>>of the package assigned by the /package naming authority.
> 
> 
> That's roughly what I had in mind.
> 
> 
>>If the AC_SLASHPACKAGE macro is not given, then a default
>>name of /package/host/gnu.org/$(PACKAGE) could be used,
> 
> But autoconf is also used for packages that the FSF has no knowlege
> of, so that risks collisions.  If the slashpackage path isn't
> specified, then autoconf should refuse to produce a
> slashpackage-capable tarball, I think.

Whatever.  It's up to you guys to decide.  All I ask is that
it be delivered, if possible, as a single autoconf macro
which the autoconf maintainers can drop into their archive.
I guess the way I'd suggest getting what you mentioned
there is to have the --/package commandline option be
sensed only by AC_SLASHPACKAGE.  Then the users could only
ask for a /package installation if the package maintainer
had specified it.

I do think it's quite important that AC_SLASHPACKAGE not
*force* the app into /package, simply that it let the user
specify it at configure time.
- Dan