Skip Menu |

This queue is for tickets about the Module-Build CPAN distribution.

Report information
The Basics
Id: 8341
Status: resolved
Priority: 0/
Queue: Module-Build
People
Owner: Nobody in particular
Requestors: bulb [...] ucw.cz
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Wed Nov 10 04:08:55 2004 Guest - Ticket created
Subject: No way to install files in bin
The script_files install files to ${install_base}/script, which is generaly bogus. Though bin directory is described in documentation of install action, there is no way (in doc, but does not seem to be in source either) to install anything to it. PS: Sorry to say that, but I have to reconsider using Module::Build for anything. It's no better than ExtUtils::MakeMaker
  Wed Nov 10 12:16:10 2004 kwilliams [...] cpan.org - Correspondence added
Don't panic... I'm not completely sure what your exact need is - do you want to make the things in script/ go somewhere else, or do you want to make scripts go into bin/ ? If it's the former, can you explain what you mean by "generally bogus"? I'm sure we can figure out something sensible. If it's the latter, I recommend not to do that - people installing your module will want to be able to set "--install_path script=/foo/bar" to control where the scripts go. -Ken
  Wed Nov 10 12:16:11 2004 kwilliams [...] cpan.org - Status changed from 'new' to 'open'
  Mon Nov 15 00:44:54 2004 mschwern [...] cpan.org - Correspondence added
From: schwern [...] pobox.com
[KWILLIAMS - Wed Nov 10 12:16:10 2004]: Show quoted text
> I'm not completely sure what your exact need is - do you want to make > the things in script/ > go somewhere else, or do you want to make scripts go into bin/ ? > > If it's the former, can you explain what you mean by "generally > bogus"? I'm sure we can > figure out something sensible. > > If it's the latter, I recommend not to do that - people installing > your module will want to be > able to set "--install_path script=/foo/bar" to control where the > scripts go.
I think he means the latter and I'd agree. ${install_base}/script is a little silly. There's no /usr/script. No OS I know of has a script directory. People don't make distinctions when installing programs between scripts and binaries. The "script" vs "binary" distinction is purely bookkeeping and only necessary to build the executable, not to use it. Finally, I don't see how this interferes with --install_path script. Patch attached so that scripts go into ${install_base}/bin.
--- lib/Module/Build/Base.pm 2004/11/15 05:43:57 1.1 +++ lib/Module/Build/Base.pm 2004/11/15 05:44:01 @@ -2303,7 +2303,7 @@ lib => ['lib'], arch => ['lib', $self->{config}{archname}], bin => ['bin'], - script => ['script'], + script => ['bin'], bindoc => ['man', 'man1'], libdoc => ['man', 'man3'], );
  Tue Nov 16 11:41:52 2004 kwilliams [...] cpan.org - Correspondence added
Hi Jan, I appreciate your thoughts. A more appropriate forum to get them addressed would be on the Module::Build list itself (see https://lists.sourceforge.net/lists/listinfo/module-build- general), since there aren't many people who watch the bugtracker. Certainly we're interested in resolving issues like the ones you raise. I recommend starting a thread for each issue you're interested in working on. -Ken
  Sun Nov 21 10:01:36 2004 kwilliams [...] cpan.org - Correspondence added
I've applied Schwern's patch to the CVS mainline (not the bugfix line), so it'll be in the next point release. -Ken\
  Sun Nov 21 10:01:38 2004 kwilliams [...] cpan.org - Status changed from 'open' to 'resolved'