Mantis - pm_gd
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3737 other minor always 2009-06-28 22:01 2010-07-26 12:20
Reporter: wbonnet Platform:  
Assigned To: dam OS:  
Priority: normal OS Version:  
Status: closed Product Version:  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
Summary: 0003737: GARNAME is invalid
Description: GARNAME of this packageis GD, it should be pm_GD. This name conflits with GD (the lib not the perl wrapper containted in this package)
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:
Issue History
Date Modified Username Field Change
2009-06-28 22:01 wbonnet New Issue
2009-08-06 20:00 dam Status new => assigned
2009-08-06 20:00 dam Assigned To => dam
2009-08-06 20:01 dam Note Added: 0006521
2009-08-06 20:02 dam Status assigned => feedback
2009-09-07 16:44 dam Note Added: 0006682
2009-09-07 22:04 wbonnet Note Added: 0006683
2009-09-19 13:42 dam Note Added: 0006725
2010-07-26 12:20 dam Status feedback => closed
2010-07-26 12:20 dam Resolution open => no change required

Notes
(0006521)
dam   
2009-08-06 20:01   
The GARNAME for CPAN modules is the exact CPAN module name, which is "GD". The GARNAME of the GD library is "gd" in lowercase. Is this sufficient?
(0006682)
dam   
2009-09-07 16:44   
William, any feedback on this?
(0006683)
wbonnet   
2009-09-07 22:04   
My point of view is that we may face the same problem later and define a standard.

Even if the CPAN module is called GD, we should use pm_gd. We may imagine soon we will have to face problem between foo pm_foo and py_foo. Each will be using FOO as its internal name.

btw uwatch is not (yet) case sensitive, but it is certainly not the good way to distinguish between (lib)GD and pm_gd
(0006725)
dam   
2009-09-19 13:42   
Maybe it is better to use the catalogname as it really has the necessity to be unique?