Re: [Fink-devel] Adding a new package for the first time
Sean's comments make a lot of sense. The manual should start with a simple example with full instructions, e.g. 1. put the following content into a file called hello.c 2. put the following content into a file called Makefile 3. type tar -chofz hello.tgz hello.c Makefile.c 4. move hello.tgz to (DIRECTORY) 5. put the following content into a file called hello.info 6. move hello.info to (DIRECTORY) 7. type (FINK COMMAND) to build a local copy 8.If step 7 worked, type (FINK COMMAND) to install the built copy in the above, you'll note that I have some items in caps. I read the manual in some detail, but I only realized these essential things after folks on this list helped me. Q: is the package manual available in WIKI form? If so, then folks like Sean (and me) could make a stab at adding content to help other newbies. Alternatively, is the package manual avail in CVS, and is there a patch facility to coordinate contributions? On 23-Jun-04, at 1:04 AM, brlcad wrote: Hello, After having gone through the process of getting a new project added to fink for the first time, I figured I might as well share some of my thoughts and insights with others. Dan E. Kelley, Associate Professorphone:(902)494-1694 Oceanography Department, Dalhousie University fax:(902)494-2885 Halifax, Nova Scotia mailto:[EMAIL PROTECTED] Canada B3H 4J1 http://www.phys.ocean.dal.ca/~kelley/Kelley_Dan.html --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Shell startup should warn if init.* fails
Just had the N+1th user on #fink remove Fink and now have his shell startup abort when it tries to load /sw/bin/init.*. There is an error message about no such file or directory and then the remainder of the dotfile is skipped. Instead of just (for csh): source _file_ should we do: [ -x _file_ ] source _file_ || echo _some_warning_ That way they get a message about what is wrong (conceptually, not a Unix-ish) but dotfile processing continues so the environment they eventually get is as usual (modulo fink) instead of some mutant. OTOH, they do lose the useful-to-Unix-folks (including us, when they come for help) actual error message about what is wrong. Thoughts? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Adding a new package for the first time
I appreciate the feedback. I wonder whether you had a chance to look at one other resource linked from the Documentation page: the slides from a talk I gave Using Fink: A Developer's How-To at the 2002 O'Reilly OS X conference. During the talk itself, I took people through the creation of a simple fink package in step by step fashion. The slides probably don't capture that too well, though... As you suggest, we really need to write a Beginner's Guide. -- Dave --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] os x 10.3.x tempnam() problem ?
Hi ! I'm experiencing problems compiling SGI FAM; OKs-Computer:/sw/src/fam/fam-2.6.10-patched/fam ikal$ make -e g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\/usr/local/etc/fam.conf\ -D__FreeBSD__ -g -O2 -c -o Listener.o `test -f 'Listener.c++' || echo './'`Listener.c++ (...) Listener.c++: In static member function `static void Listener::create_local_client(TCP_Client, unsigned int)': Listener.c++:208: error: `tempnam' undeclared (first use this function) Listener.c++:208: error: (Each undeclared identifier is reported only once for each function it appears in.) make: *** [Listener.o] Error 1 Browsing the web for the tempnam() function, it found out that: #include sys/types.h is needed to make use of this function. This is the case in Listener.c++ Some users report that this function is broken on os x... I'm not able to say ... so I looked up in the Fink FAQ, section 6 and 7, and found nothing special about tempnam() known problems. Can someone tell me if tempnam() is really broken on os x, and what is the workaround to this problem ? Should I have to download these 21*31Mbytes files for the X-Code 1.2 Update ? Nothing specified about a tempnam() problem on the following page: http://developer.apple.com/documentation/ReleaseNotes/DeveloperTools/GCC3.html Maybe am I doing something wrong and really obvious ? Olivier --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: [Fink-beginners] Application launchers for Fink programs
(I'm redirecting this onto the fink-devel list. Kevin, if you wouldn't mind subscribing to that so that we can continue the conversation there, that would be great.) Kevin, As you have surmised, the essential thing that is needed in order to create a fink package is a step by step list of instructions to be followed. My guess is that you've used some of the GUI developer tools for building your .app, but there are generally command-line versions of the same steps, which is what we'll need for the fink .info file. If you can give us a brief outline of the steps you follow, we can probably collectively work out how to make them into a fink .info file. My guess is that when all is said and done, you'll need to supply on your site a tarball containing the applescript as well as things like the icon resource file. -- Dave Kevin Walzer [EMAIL PROTECTED] wrote: Dave, Sure, I'd be happy to have these run as Fink packages, especially if they're useful. What I'm not clear on is how to package them, how to provide source code, etc. The AppleScript is very simple to write (which is why I can do it), but putting the binaries together so that they have a nice icon and associate with the correct file extension involves more work. But the steps are pretty straightforward and I'd be glad to document them (I'm thinking about putting a tutorial up at my website). Just let me know what I should do. It's kind of cool that Fink wants to pick these up. In researching on how to put the code together, and looking at code snippets on various websites, I saw that someone thanked Martin Castobel for assistance in developing the code I was looking at, so this sort of brings things full circle. Martin has been very helpful to me over the past year in troubleshooting various Fink install issues, especially Scribus (which I'm now using in a production setting in my day job as a book publisher). I'm working on another launcher for Inkscape, and will have that ready for release soon as well. Thanks, Kevin David R. Morrison wrote: | Kevin, | | Those look great! Thanks for telling us about them. | | The Fink developers agreed some months ago to start allowing .app's in Fink | packages, although there aren't really any examples yet. Would you be willing | to have your application launchers set up as Fink packages? The advantage, | of course, is that someone who uses Fink to install the application launcher | will find that Fink automatically installs ethereal or scribus, as required | by the launcher. | | -- Dave | | | Kevin Walzer [EMAIL PROTECTED] wrote: | | |I've developed two AppleScript app launchers for Fink applications that |may be of interest to the list--AquaScribus and AquaEthereal. Both |activate their respective Fink applications (Scribus and Ethereal) by |double-clicking an icon, and AquaScribus also allows you to launch |Scribus by double-clicking a Scribus (.sla) file. You can find links for |their home pages and downloads at | http://www.wordtech-software.com/aqua.html . The downloads include the |source AppleScript code and are released under the GPL. | |Note: These are app launchers *only* and do not repackage any binaries |or code maintained by the Fink developers; they call the appropriate |Fink program from the /sw/ directory. | |- -- |Kevin Walzer, PhD |WordTech Software--Open Source Applications and Packages for OS X |http://www.wordtech-software.com |http://www.smallbizmac.com |mailto:[EMAIL PROTECTED] | | | | - -- Kevin Walzer, PhD WordTech Software--Open Source Applications and Packages for OS X http://www.wordtech-software.com http://www.smallbizmac.com mailto:[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFA2b/vF6m9qPmThLQRAhF2AJ9exQfjnrxk2zNuu99kMDI0ORPgAACeJuvN jbB6HXFLWxUYCIKsLky67ww= =GCme -END PGP SIGNATURE- --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] os x 10.3.x tempnam() problem ?
On Wed, Jun 23, 2004 at 06:54:37PM +0200, Olivier Kaloudoff wrote: I'm experiencing problems compiling SGI FAM; OKs-Computer:/sw/src/fam/fam-2.6.10-patched/fam ikal$ make -e g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\/usr/local/etc/fam.conf\ -D__FreeBSD__ -g -O2 -c -o Listener.o `test -f 'Listener.c++' || echo './'`Listener.c++ (...) Listener.c++: In static member function `static void Listener::create_local_client(TCP_Client, unsigned int)': Listener.c++:208: error: `tempnam' undeclared (first use this function) Listener.c++:208: error: (Each undeclared identifier is reported only once for each function it appears in.) make: *** [Listener.o] Error 1 Browsing the web for the tempnam() function, it found out that: #include sys/types.h is needed to make use of this function. This is the case in Listener.c++ Various different platforms have their .h organized differently. On my OS X machine, the manpage for tempnam() says that this function is declared in stdio.h. But let's check just to be sure: % grep -lr tempnam /usr/include /usr/include/libc-gcc3.p /usr/include/php/ext/standard/file.h /usr/include/php/main/config.nw.h /usr/include/php/main/php_config.h /usr/include/stdio.h Some users report that this function is broken on os x... I'm not able to say I Googled for 'tempnam os x' and all the bug-reports I see mention OS X 10.0.x, or a general (not OS X specific) caveat about using this function (which is also mentioned in the manpage). Perhaps these users could be more specific about OS X version, and their own symptoms or other specific source of info? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Type:ruby field docs and splitting gnome2-rb18
Hi, I submitted a package for the ruby bindings to some gnome2 libs: https://sourceforge.net/tracker/index.php? func=detailaid=963608group_id=17203atid=414256 By looking at other packages and thanks to someone on IRC I could use the Type: ruby field, but as this field is not documented (on the website at least) I'm not sure if this is correct, though it seems to work. Second, I was lazy and made one big package for all libs with all dependancies. Which is the best way to split it? After reading the packaging docs I'm still not sure if I could use splitoffs or Info: subpackages... Do I really need to write 14 similar .info files? regards, -- D. --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] /sw/bin/perl
Hi, The following is the latest example _ but I had this on numerous occasions : ___attempted build of arts-latest /var/tmp/tmp.1.LaILav the following environment is being used: ACLOCALFLAGS: -I libltdl CFLAGS: -Os -fPIC CPPFLAGS: -I/sw/lib/flex/include -fno-common -no-cpp-precomp -DMACOSX -DARTS_NO_ALARM -I/sw/include -I/usr/X11R6/include CXXFLAGS:-Os -fPIC FREETYPE_CONFIG: /usr/X11R6/bin/freetype-config LDFLAGS: -L/sw/lib/flex/lib LIBS: -L/sw/lib -L/usr/X11R6/lib PATH: /sw/lib/flex/bin:/sw/share/Geomview/bin:/sw/bin:/sw/sbin:/bin:/usr/bin: /sbin:/usr/sbin:/usr/X11R6/bin:/usr/X11R6/bin PKG_CONFIG_PATH: /sw/lib/flex/lib/pkgconfig ./admin/cvs.sh: /sw/bin/autoheader-2.59: /sw/bin/perl: bad interpreter: No such file or directory *** AUTOHEADER NOT FOUND!. ___ This type of thing is due to having at some time used a perl-xyz from fink, (in this case when last building autoconf2.5 _ but many other pkgs have the problem), and then switching back to Apple's perl (eg, because perllib didn't build shared in perl584). I think it is impossible to ask all involved pkg's to take appropriate precautions to avoid this possibility. The obvious thing that comes to mind is that fink ensures _ probably through system-perl (and the various placeholders system-perlxyz) _ that /sw/bin/perl is ALWAYS a symlink to the 'currently active perl'. Would this be difficult ? Or a bad idea ? Jean-Francois Mertens --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: /sw/bin/perl
jfm wrote: ./admin/cvs.sh: /sw/bin/autoheader-2.59: /sw/bin/perl: bad interpreter: No such file or directory *** AUTOHEADER NOT FOUND!. This type of thing is due to having at some time used a perl-xyz from fink, (in this case when last building autoconf2.5 _ but many other pkgs have the problem), and then switching back to Apple's perl (eg, because perllib didn't build shared in perl584). ...not necessarily... I think it is impossible to ask all involved pkg's to take appropriate precautions to avoid this possibility. The obvious thing that comes to mind is that fink ensures _ probably through system-perl (and the various placeholders system-perlxyz) _ that /sw/bin/perl is ALWAYS a symlink to the 'currently active perl'. I saw this type of error recently too; it happened because system-perl provides perl581-core, but not perl581. So when something wants some perl module installed that's Provided by perl581, you end up with a *real* perl581, but a *virtual* perl581-core, and get this error. The actual error is that /sw/bin/perl can't find /sw/lib/foo/libperl.dylib that it's linked against. -- Benjamin Reed, a.k.a. RangerRick [EMAIL PROTECTED] / http://ranger.befunk.com/ --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: /sw/bin/perl
Jean-Francois, I'm not sure if it's the same error you are seeing, but one bug I am aware of is this: there is a place in the fink code where fink tests to see which is the current version of perl installed on the system... unfortnately, fink seems to cache this value in the database. So if you add or remove a fink package (switching between /usr/bin/perl and /sw/bin/perl), but don't run fink index, you get into trouble. -- Dave --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: /sw/bin/perl
you end up with a *real* perl581, but a *virtual* perl581-core, and get this error. Well, that can't be the right explanation, because there isn't a real perl581 package at all. -- Dave --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: /sw/bin/perl
On Jun 23, 2004, at 10:54 PM, David R. Morrison wrote: Jean-Francois, I'm not sure if it's the same error you are seeing, but one bug I am aware of is this: there is a place in the fink code where fink tests to see which is the current version of perl installed on the system... unfortnately, fink seems to cache this value in the database. So if you add or remove a fink package (switching between /usr/bin/perl and /sw/bin/perl), but don't run fink index, you get into trouble. No, not this error [ fink index runs already much too often here...-) ] Cf my msg from 2 min ago Best JF --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: /sw/bin/perl
Sorry, I meant add or remove a perl package not add or remove a fink package... --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: /sw/bin/perl
On Jun 23, 2004, at 10:51 PM, David R. Morrison wrote:
you end up with a
*real* perl581, but a *virtual* perl581-core, and get this error.
Well, that can't be the right explanation, because there isn't a real
perl581 package at all.
Correct .
It is due to the fact that a number of pkgs install scripts beginning
with
#!/currently/active/perl
# egrep -rI '\#\! */sw/bin/perl' /sw/{{s,}bin,libexec}/tmp/lst; wc -l
/tmp/lst
124 /tmp/lst
JF
---
This SF.Net email sponsored by Black Hat Briefings Training.
Attend Black Hat Briefings Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Adding a new package for the first time
Dave, Actually, when I made my first stab at the documentation a couple months ago, I recall that I did run across the presentation pdf. From memory, I believe I glanced through that and finally getting to the .info example and thinking okay, this looks like it'll be pretty simple.' There was just enough uncertainty, though, as to what goes where and what I needed to do since, as you well know, there is no accompanying text. So my fink learning adventure proceeded to the Package Manual where I quickly began to lose steam. Looking back at the presentation now, and after having gone through the process finally, I see that it is _really_ close to what I was looking for actually. Coupled with some text that was most likely given verbally during the presentation and converted to html (or reformat pdf away from slide-format), it would serve as a great intro. It'd still probably be very useful to point users to the vast array of existing .info files in fink already for other projects. I believe I ultimately visited about a dozen to get a feel for convention and ideas of things to check for. Anyhow, thanks again for the great work! Cheers! Sean On Jun 23, 2004, at 08:51, David R. Morrison wrote: I appreciate the feedback. I wonder whether you had a chance to look at one other resource linked from the Documentation page: the slides from a talk I gave Using Fink: A Developer's How-To at the 2002 O'Reilly OS X conference. During the talk itself, I took people through the creation of a simple fink package in step by step fashion. The slides probably don't capture that too well, though... As you suggest, we really need to write a Beginner's Guide. -- Dave --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Re: /sw/bin/perl
On Jun 23, 2004, at 10:57 PM, jfm wrote: It is due to the fact that a number of pkgs install scripts beginning with #!/currently/active/perl More accurately probably, #! `which perl` Cf all 'checking for perl... /sw/bin/perl' in log files JF --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Re: /sw/bin/perl
On Thu, Jun 24, 2004 at 12:18:51AM +0200, jfm wrote: More accurately probably, #! `which perl` #! /usr/bin/env perl which will actually work. There are a lot of strange restrictions on that line. Dave Brown --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Re: /sw/bin/perl
David Brown wrote: On Thu, Jun 24, 2004 at 12:18:51AM +0200, jfm wrote: More accurately probably, #! `which perl` #! /usr/bin/env perl which will actually work. There are a lot of strange restrictions on that line. Most of these packages allow the user to override their tests for perl by checking the PERL environment variable first. If we just have fink set PERL to /usr/bin/perl by default (different default for perl modules, I guess), then the problem will go away. Peter -- Peter O'Gorman - http://www.pogma.com --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Type:ruby field docs
Damien Pollet [EMAIL PROTECTED] wrote: I submitted a package for the ruby bindings to some gnome2 libs: https://sourceforge.net/tracker/index.php? func=detailaid=963608group_id=17203atid=414256 By looking at other packages and thanks to someone on IRC I could use the Type: ruby field, but as this field is not documented (on the website at least) I'm not sure if this is correct, though it seems to work. Yes, the lack of documentation is my fault, and I intend to eventually remedy it. I'd love to get some input as to what people would like to see documented (also, how people would like Type: ruby to work; I implemented the field based on limited experience with ruby and a limited number of ruby modules). Matthias --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
