Skip Menu |

This queue is for tickets about the CPANPLUS CPAN distribution.

Report information
The Basics
Id: 4143
Status: resolved
Priority: 0/
Queue: CPANPLUS
People
Owner: Nobody in particular
Requestors: schwern [...] pobox.com
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Fri Oct 17 09:47:00 2003 Guest - Ticket created
Subject: CPANPLUS improperly glomming together make arguments
CPANPLUS allows you only one configuration value for extra arguments to pass to make. It then proceedes to pass these arguments to all stages of the build process whether its "make" or "make test" or "make install". For example, if I set my makeflags to be "UNINST=1" it will run "make UNINST=1", "make test UNINST=1", "make install UNINST=1". CPANPLUS gets away with this because *usually* the make flags only make sense to a single stage of the build. However, I wouldn't trust this to always be the case. CPANPLUS needs to allow seperate make flags for "make", "make test" and "make install".
  Thu Nov 11 07:41:43 2004 kane [...] cpan.org - Status changed from 'new' to 'resolved'
  Thu Nov 11 07:41:43 2004 kane [...] cpan.org - Correspondence added
[guest - Fri Oct 17 09:47:00 2003]: Show quoted text
> For example, if I set my makeflags to be "UNINST=1" it will run "make > UNINST=1", "make test UNINST=1", "make install UNINST=1". > > CPANPLUS gets away with this because *usually* the make flags only > make sense to a single stage of the build. However, I wouldn't > trust this to always be the case. > > CPANPLUS needs to allow seperate make flags for "make", "make test" > and "make install".
Under the flag of 'better late than never' -- cpanplus 0.050 only passes these flags to 'make' not 'make test' or 'make install'. It seems so far that these flags only make sense at 'make' time anyway... if not, patches are welcome (against 0.050 :)