Re: [Module-build-general] read_config()?

[Scott B. <lis...@ni...>]

On Thu, 22 May 2003 09:42:24 -0500, Ken Williams wrote:
> 
> Sorry I didn't have time to respond before you made your patches, they 
> won't really work unfortunately.

	Don't worry about that. The patch was easy to generate and
	I learned a lot about Module::Build.

> The META.yml is created when the distribution is created, i.e. right 
> before the distro is uploaded to CPAN or otherwise made available.  It 
> does *not* get re-created when users download, build, and install the 
> module, because they don't typically run the 'distdir' action.

	In that case I may need a different approach. Among other
	things, I need to know how the user is configuring their
	installation.

	One of the constraints I have is I try to run in taint mode.
	Not set-uid, but in taint mode none the less. (Exposed
	network service => extreme paranoid mode.) Therefore using
	PERL5LIB to find non-standard install directories won't
	work. Instead I may need to hard code "use lib '...'" in
	some scripts.

	I'll play around with my architecture and see if I can tweak
	my implementation to avoid this issue. I can also fall back
	on the dummy Module::Build object to read the configuration
	directly.

> All the scripts are run from the top level of the distribution, so the 
> path to META.yml is always just 'META.yml' in the current directory.

	You are right, I should be able to count on that.

> > 	One last request, the hash passed into Module::Build::new()
> > 	should have a field dedicated to the calling module's private
> > 	data. ...
> >
> > 		...
> 
> This is a good idea in principle.  Before implementing it though, we'd 
> have to figure out how it interacts with command-line arguments, both 
> to the Build.PL script and to individual actions invoked later.

	I don't mind if you change how it is done. I want that sort
	of functionality moving forward and would prefer to use a
	supported technique instead of polluting Module::Build
	structures.

		Scott