INN::Config Perl module

[Russ Allbery]

Julien ÉLIE <julien at trigofacile.com> writes:
> En réponse à Russ Allbery :

>>> * I have created trunk/lib/perl/INN/Config.pm.in (Config.pm
>>>   is generated at configure time) and trunk/lib/perl/Makefile;
>>>   a configure option --with-libperl-dir (=${libdir}/perl by
>>>   default) allows to change the install directory (in case
>>>   some packages will want to put INN::Config with all the
>>>   other Perl modules).  Is that OK?

>> I would create a separate top-level perl directory instead of lib/perl to
>> keep the directory nesting from getting too extreme, but otherwise that
>> seems okay to me.

> All right.
> For both the SVN and the final installation directory?

No, just for Subversion.  The final installation directory should be under
lib for the way that INN is currently laid out.  (It should really be
under share, but that's another problem.)

> Let's begin in a simple way (configure option and copy when "make
> install").  The module as it is now is fairly basic (perhaps lame for
> Perl gurus like you) since it only consists in declaring "our $newsbin =
> ..." and allowing its export if claimed.

> I have not documented it (with an embedded POD in the module) because
> there is not much to say right now and maybe the definitive
> implementation of INN::Config will change.  But it will be good to
> document innshellvars* and INN::Config within it to have a decent man
> page.

Yup.

> So let's keep innshellvars.pl for backward compatibility.  I will add
> a disclaimer at the beginning of the file to say that INN::Config should
> be used.

> But innshellvars.pl will not be used by fixscript.

That sounds good.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.