Daniel Echeverry <[email protected]> writes: > I am working in a new version of lfm, the new version is python3 for > this reason I want to know if necessary create a ITP bug with a new > package like this lfm3, to package this new version
The name ‘lfm3’ implies you are packaging version 3 *of lfm*. Is that the case for this package? To put the version of LFM in the package name also implies LFM 3 and some other version of LFM (version 2, or version 4, etc.) are likely candidates to be installed on the same system. Is that true for this case? The implementation language of the program is generally quite irrelevant to what the program should be called. An exception would be if the program's purpose is primarily *about* that language, such as a development tool for that language. Is that the case for this program? > or if I could continue with the same package. If the change of implementation doesn't entail a significant change in how the program is expected to behave, then yes, I think keeping the package name the same is important to reflect that continuity. -- \ “Generally speaking, the errors in religion are dangerous; | `\ those in philosophy only ridiculous.” —David Hume, _A Treatise | _o__) of Human Nature_, 1739 | Ben Finney
