On Sat, Jul 09, 2005 at 01:44:46PM -0400, Koen van der Drift wrote: > Hi, > > (repost from April 2005) > > I recently took over maintainership for the package > 'python-biopython-py'. However, I think the name biopython-py would be > more appropriate.
I agree. > Unless there is a special reason why (some) python. packages have > the python prefix, although most don't. So upstream programs really do call themselves "python-foo", and some other package managers use "python-" as a naming convention for python modules. > Would it be a big problem, if I rename the package? I can leave in > the old info files, and add the new ones. The new ones will only be > updated in the future. One problem is compatibility with other packages. Do any others depend on this one? If so, they must all be fixed to use the new name at the same time as the name changes. A second problem is how the user who has the old-name package installed will know about this upgrade...his old-name-1.0-1 isn't marked out-of-date when new-name-2.0-1 appears. One solution is to create a final old-name-2.0-1:Depends:new-name(>=2.0-1) but is Type:bundle and has a Description noting that it's just a upgrade compatibility game. That way his old old-name will be out-of-date, and when he upgrades it he will get he'll get the new one. A more long-range solution would be to implement an Obsoletes field... if foo:Obsoletes:bar, any version of foo would be seen as newer than every version of bar, and dpkg would make some intelligent decisions about automatically trying to remove bar. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
