[Fink-devel] readline ready for stable?
For me, the new readline-shlibs has worked quite fine for some time now. Can others confirm this? If yes, it should be moved ASAP to stable since other packages are pending simple because they now depend on readline-shlibs... Max -- --- Max Horn Software Developer email: mailto:[EMAIL PROTECTED] phone: (+49) 6151-494890 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] readline ready for stable?
Do agree, and is working fine for me. Matt On Monday, March 18, 2002, at 12:39 AM, Max Horn wrote: For me, the new readline-shlibs has worked quite fine for some time now. Can others confirm this? If yes, it should be moved ASAP to stable since other packages are pending simple because they now depend on readline-shlibs... ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] shlibs
If I understand correctly what the dpkg shlibs stuff will eventually do for us, at some point in the future each fink package which provides shared libraries will need to give some data about those libraries to be used by the dpkg-shlibs system. Max, will we put this directly in the .info file, do you think? Something like Shlibs: zlib 1 zlib (= 1.1.4) (to use the example from the Debian policy manual http://www.debian.org/doc/debian-policy/ch-sharedlibs.html ) Or maybe it goes in a separate file? The reason for bringing this up now is it would be good to start encouraging people to provide this information in their packages, pretty soon. To avoid fink validate problems, we might want to add one more field (Shlibs) to the list of known fields right now, before the package manager release. -- Dave ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] readline ready for stable?
If the functionality of command history in python-2.2-8 is any indication, readline-shlibs works very well indeed. On Sunday, March 17, 2002, at 07:21 AM, David R. Morrison wrote: readline-shlibs works well for me also. I think it is ready to move. -- Dave ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] shlibs
At 10:47 Uhr -0500 17.03.2002, David R. Morrison wrote: If I understand correctly what the dpkg shlibs stuff will eventually do for us, at some point in the future each fink package which provides shared libraries will need to give some data about those libraries to be used by the dpkg-shlibs system. Max, will we put this directly in the .info file, do you think? Yes Something like Shlibs: zlib 1 zlib (= 1.1.4) More like Shlibs: libz 1 zlib (= 1.1.3) Though I don't like that to much... this is really something where XML would be handy. (to use the example from the Debian policy manual http://www.debian.org/doc/debian-policy/ch-sharedlibs.html ) Or maybe it goes in a separate file? No, why would we put it into a seperate file? One main strength of Fink is that everything for a package is in a single .info file (OK, in some cases, there's an additional .patch file). The reason for bringing this up now is it would be good to start encouraging people to provide this information in their packages, pretty soon. To avoid fink validate problems, we might want to add one more field (Shlibs) to the list of known fields right now, before the package manager release. I disagree. It's completly useless to do so now, since we first have to research how exactly it would be done. I.e. we'd end up with a bunch of package using some format we think now is good, only to discover they all have to be redone then. I.e. I don't see benefits from doing this now. We have enough other things to do first which are more urgent. Max -- --- Max Horn Software Developer email: mailto:[EMAIL PROTECTED] phone: (+49) 6151-494890 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] db3 / db4
OK, I just moved readline to stable, and also neon. Now, what about db3 / db4 ? Can we move those? I had no problem reports on them for a long time. MAx -- --- Max Horn Software Developer email: mailto:[EMAIL PROTECTED] phone: (+49) 6151-494890 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Planning this mail - comment please
I plan to send out the following mail to fink-beginners, fink-user, and fink-announce. Please tell me what you think of it, if should forget the idea, or change something about it; you may also want to suggest changes to the list of important package I gave (I tried to keep it short, but obviously, everybody will have a different opinion on what is important). Dear Fink user, we, the Fink team, would like to make a new full Fink release in the near future. For this, we'd like to move as many package to stable as possible. But to be able to do so, we need *your* help! Under http://fink.sourceforge.net/pdb/testing.php, you can find a long list of packages which are in unstable, but not yet in stable. And it's a long list (over 550 packages). Please, look through this list. If you see packages you are using succesfully, please report it to the package maintainer, so that he can decide to move that package to stable. You can find out the email address of the maintainer by clicking on the link for each package; or alternatively, you can enter fink info PACKAGE to see the maintainer of any given package. Some package that would especially important to see in stable (so look for those first): apache bash db3 / db3-bin / db3-doc / db3-shlibs db4 / db4-bin / db4-doc / db4-shlibs freetype2 / freetype2-shlibs gimp glib / glib-shlibs all gnome packages mysql orbit xfree86-base 4.2.0-4 and xfree86-rootless 4.2.0-2 But don't limit yourself to these, *any* package is important! Just remember, Fink is a group effort. We can't do without your help! Thank you for helping, Max Horn Fink Lead Developer ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Planning this mail - comment please
looks good to me, thought qt and bind9 should be added to the list IMHO. But I think it's a good email to send like once week :P [EMAIL PROTECTED] writes: I plan to send out the following mail to fink-beginners, fink-user, and fink-announce. Please tell me what you think of it, if should forget the idea, or change something about it; you may also want to suggest changes to the list of important package I gave (I tried to keep it short, but obviously, everybody will have a different opinion on what is important). ¸.·´^`·.,][JFH][`·.,¸¸.·´][JFH][¸.·´^`·., Justin F. Hallett - Systems Analyst Phone: (780)-408-3094 Fax: (780)-454-3200 E-Mail: [EMAIL PROTECTED] .·´^`·.,][JFH][`·.,¸¸.·´][JFH][¸.·´^`·., ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] shlibs
Max Horn [EMAIL PROTECTED] wrote: The reason for bringing this up now is it would be good to start encouraging people to provide this information in their packages, pretty soon. To avoid fink validate problems, we might want to add one more field (Shlibs) to the list of known fields right now, before the package manager release. I disagree. It's completly useless to do so now, since we first have to research how exactly it would be done. I.e. we'd end up with a bunch of package using some format we think now is good, only to discover they all have to be redone then. I.e. I don't see benefits from doing this now. We have enough other things to do first which are more urgent. I didn't express myself very well. Someday, later, we will want to introduce Shlibs and start to use it. If we are sure that this will be the name of the field, it would be nice to have fink validate not object to it. (Causes less confusion when we actually start to use it.) We don't make point releases of the fink package manager very often, so I thought it would be good to include this field now for future use (like we did with the BuildDependsOnly field). -- Dave ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Planning this mail - comment please
Excellent idea, I'd include aalib and libmpeg as the gimp needs these and samba as well. Matt On Monday, March 18, 2002, at 05:19 AM, Max Horn wrote: I plan to send out the following mail to fink-beginners, fink-user, and fink-announce. Please tell me what you think of it, if should forget the idea, or change something about it; you may also want to suggest changes to the list of important package I gave (I tried to keep it short, but obviously, everybody will have a different opinion on what is important). ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Planning this mail - comment please
My point of view about the dependent packages is this: if a user tells us that he/she is successfully using the latest version of package foo, then we know that he/she is also successfully using at least some version of everything that foo depends on (even if the user doesn't point that out explicitly). This amplifies the feedback somewhat! -- Dave ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] shlibs
I fully agree with this, it hurts on one to have them but helps us developpers in the mean time. [EMAIL PROTECTED] writes: Someday, later, we will want to introduce Shlibs and start to use it. If we are sure that this will be the name of the field, it would be nice to have fink validate not object to it. (Causes less confusion when we actually start to use it.) We don't make point releases of the fink package manager very often, so I thought it would be good to include this field now for future use (like we did with the BuildDependsOnly field). ¸.·´^`·.,][JFH][`·.,¸¸.·´][JFH][¸.·´^`·., Justin F. Hallett - Systems Analyst Phone: (780)-408-3094 Fax: (780)-454-3200 E-Mail: [EMAIL PROTECTED] .·´^`·.,][JFH][`·.,¸¸.·´][JFH][¸.·´^`·., ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Localizations required, once more
I changed some UI stuff in the GroupcChat preference dialog, the french localization needs to be updated for that. Also, it seems that GroupChat hasn't yet been localized to Spanish - Cesar, can you do that, would be nice to have it for the near release. Cheers, Max -- --- Max Horn Software Developer email: mailto:[EMAIL PROTECTED] phone: (+49) 6151-494890 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] feedback on unstable packages
Dear Fink Developers, I noticed that you were about to solicit feedback regarding unstable packages so I decided to take a risk and enable the unstable directory via /sw/etc/fink.conf and then upgrade all my packages (using source update as of today). I am not entirely sure which of these are stable and which are unstable, but here is the list of what I now have. All these packages appear to be working fine. (By the way it is hard to send messages about individual packages directly to the package maintainers when there are no e-mail addresses provided for them.) Thanks for provided such a great product, -Aaron Seitz Here is my list of packages: i aalib 1.4rc4-4Ascii art library i aalib-bin 1.4rc4-3Ascii art library i aalib-shlibs1.4rc4-3Ascii art library i apt 0.5.4-1 Advanced front-end for dpkg i audiofile 0.2.3-3 Audio File Library i audiofile-shlib 0.2.3-3 Audio File Library i base-files 1.5-1 Directory infrastructure i bzip2 1.0.1-4 Block-sorting file compressor i daemonic20010902-1 Interface to daemon init scripts i darwin 5.3-1 [virtual package representing the kernel] i debianutils 1.15-4 Misc. utilities specific to Debian (and Fink) i dlcompat20020120-1 Dynamic loading compatibility library i dpkg1.9.17-2The Debian package manager i emacs 20.7-5 Extremely flexible real-time display editor i esound 0.2.23-3Enlightened Sound Daemon i esound-bin 0.2.23-2Enlightened Sound Daemon i esound-data 0.2.23-2Enlightened Sound Daemon i esound-shlibs 0.2.23-2Enlightened Sound Daemon i fink0.9.8-1 The Fink package manager i gettext 0.10.40-2 Message localization support i ghostscript 7.02-2 Interpreter for the PostScript language and... i ghostscript-fon 6.0-3 Standard fonts for Ghostscript i gimp1.2.3-3 The GNU Image Manipulation Program i glib1.2.10-4Common C routines used by Gtk+ and other libs i glib-shlibs 1.2.10-4Common C routines used by Gtk+ and other libs i gnome-libs 1.4.1.4-2 Base libraries for GNOME i gtk+1.2.10-5The Gimp Toolkit i gv 3.5.8-3 X11 interface for ghostscript interpreter. i gzip1.2.4a-5File compressor for gz file types i icewm 1.0.9-1 Window manager with Windows, OS/2 and Motif... i imlib 1.9.10-4General image handling library for X11 and Gtk i ispell 3.2.06-2Interactive spell-checker i latex2html 2K.1beta-8 Converts LaTeX documents to HTML i libiconv1.7-3 Character set conversion library i libjpeg 6b-4JPEG image format handling library i libjpeg-bin 6b-3JPEG image format handling library i libjpeg-shlibs 6b-3JPEG image format handling library i libmpeg 1.3.1-2 Gimp MPEG library i libmpeg-shlibs 1.3.1-2 Gimp MPEG library i libpng 1.0.12-5PNG image format handling library i libpng-shlibs 1.0.12-5PNG image format handling library i libtiff 3.5.7-6 TIFF image format library and tools i libtiff-bin 3.5.7-5 TIFF image format library and tools i libtiff-shlibs 3.5.7-5 TIFF image format library and tools i libungif4.1.0b1-2 GIF image format handling library, LZW-free... i libxml2 2.4.13-1XML parsing library, version 2 i lyx 1.1.6fix4-1 High level wordprocessor utilizing the LaTe... i macosx 10.1.3-1[virtual package representing the system] i ncurses 5.2-6 Full-screen ascii drawing library i netpbm 9.24-3 Graphics manipulation programs and libraries i netpbm-bin 9.24-2 Graphics manipulation programs and libraries i netpbm-shlibs 9.24-2 Graphics manipulation programs and libraries i openssh 3.1p1-1 Secure shell (remote login) client and server i openssl 0.9.6c-1Secure Sockets Layer and general crypto lib... i orbit 0.5.13-3The CORBA ORB used in GNOME i orbit-bin 0.5.13-2The CORBA ORB used in GNOME i orbit-shlibs0.5.13-2The CORBA ORB used in GNOME i passwd 20020307-1 User and group entries for daemons i readline4.2a-4 Comfortable terminal input library i readline-shlibs 4.2a-4 Comfortable terminal input library i rxvt2.7.8-1 rxvt (ouR XVT) - a VT102 emulator for the X... i system-tetex20010808-5 Placeholder package for teTeX i tar 1.13.19-1 GNU tape archiver i tightvnc1.2.2-1 Enhanced version of VNC. i type1inst 0.6.1-3 Type 1 PostScript font installation utility i xaw3d 1.5-3 Athena widget set with 3D look i xdvi22.54-1
Re: [Fink-devel] feedback on unstable packages
Thanks for the feedback, to get the email address for the maintainer of a particular package just type 'fink info packagename' :) Matt On Monday, March 18, 2002, at 01:23 PM, Aaron Seitz wrote: (By the way it is hard to send messages about individual packages directly to the package maintainers when there are no e-mail addresses provided for them.) ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
