Re: [Fink-devel] renaming a package
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
Re: [Fink-devel] build error: directory
On Jul 10, 2005, at 9:36 PM, Jesse Alama wrote: When the file emacs-wiki_2.68.orig.tar.gz, which is downloaded from the debian, is unpacked it creates the directory `emacs-wiki'. Judging from the final error message, it seems that fink expects the unpacked file to be called something else, though, namely `emacs-wiki_2.68.orig'. Yes, you need to use a SourceDirectory field. Please see its entry in the packaging manual. Dave PGP.sig Description: This is a digitally signed message part
[Fink-devel] flex-1:2.5.4a-4
-- Package manager version: 0.24.7 Distribution version: 0.8.0.cvs Mac OS X version: 10.4.1 December 2001 Developer Tools gcc version: 8 make version: 3.79.1 Feedback Courtesy of FinkCommander Worked 100% Thanx Steve --- 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
Re: [Fink-devel] renaming a package
On Jul 11, 2005, at 2:03 AM, Daniel Macks wrote: 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. That sounds like a good plan. If I use Type: bundle, how do I add the variants, so that the user can define the python version she wants to use? thanks, - Koen. --- 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
Re: [Fink-devel] renaming a package
On Mon, Jul 11, 2005 at 03:51:28PM -0400, Koen van der Drift wrote: On Jul 11, 2005, at 2:03 AM, Daniel Macks wrote: 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. That sounds like a good plan. If I use Type: bundle, how do I add the variants, so that the user can define the python version she wants to use? I think same as usual...multivariants give you every combination of the choice sets. And omitting an explicit for a type key set means there's only one choice for this key, so the long-existing Type:bundle is now just a special case of the generic variant syntax. Perhaps: Package: foo-py%type_pkh[python] Type: bundle, python (2.3 2.4) would give you packages foo-py23 and foo-py24, each of Type:bundle. 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
Re: [Fink-devel] renaming a package
On Jul 11, 2005, at 3:58 PM, Daniel Macks wrote: Type: bundle, python (2.3 2.4) Ah, I didn't realize I could add two arguments to the Type field. I'll try it out. thanks, - Koen. --- 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
