[Fink-devel] Re: improvement suggestion
Pejvan BEIGUI pejvan at online.fr writes: I've got a simple request regarding the way fink handles unsuccessful downloads. I like to launch the $fink update-all before going to sleep or going out so that everything's done when I'm not actually using the computer. Have you tried 'fink -y update-all'? (from memory; it may be 'fink update-all -y' or something-- I'm not near a Mac ATM.) -- - Charles Lepple --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
[Fink-devel] Re: A suggestion
Corey Halpin [EMAIL PROTECTED] said: In working with my packages, I've written a little script that uses otool -L and dpkg -S to figure out what my package needs to depend on. Good idea. This approach gives packages that need not be specified explicitly (if they are dependencies of dependencies) but this gives a good starting point. I don't know my around fink (the program) well enough to add this myself, but I thought it might be helpful if there were something that did a trick like this one to verify that a .info depends on all the libraries it needs. Because of my previous comment, this cannot be used for if we find something not in Depends, then crash. More importantly, virtual (Provides) packages do not contain files (the files are part of the actual Package which Provides the virtual), so even if we ban implicit dependencies, we'd have to do a lot of pkg-info back-tracking to figure out whether a given otool-detected .dylib is covered by a Depends. Things like this are very useful, but I think it would take a *lot* of work to make it deterministic enough for a build-phase (or even validator) check. Someone on -devel or #fink (perhaps jfm?) has a giant shell pipeline version of this (and that covers a lot of weird corner cases), that I encapsulated as fink-dep-check in my experimental dir. 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] Re: A suggestion
Daniel E. Macks wrote: Corey Halpin [EMAIL PROTECTED] said: In working with my packages, I've written a little script that uses otool -L and dpkg -S to figure out what my package needs to depend on. Good idea. This approach gives packages that need not be specified explicitly (if they are dependencies of dependencies) but this gives a good starting point. Yeah. A starting point was all I was looking for. There's never going to be an automated way to verify that a package depends on all the right things, there are just too many ways to depend. You could call out to a program (from a script, or with some fork/exec from a program), you could do a perl use (or the same thing in your interpreted language of choice) , you could need to open a config file from another package... But if you have a binary that isn't statically linked, you'll be able to tell what it links to. There should be an automated way to make sure that the dependence tree rooted in your package does contain everything your binaries link to. I think. :-) *snip* Someone on -devel or #fink (perhaps jfm?) has a giant shell pipeline version of this (and that covers a lot of weird corner cases), that I encapsulated as fink-dep-check in my experimental dir. Cool. It didn't occur to me to look for (and through) people's experimental directories. If I were looking for your experimental dir, would I be able to find it in cvs somewhere? Or does it just live in your sandbox on your machine? thank you, crh --- 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: A suggestion
On Jul 2, 2004, at 1:55 PM, Corey Halpin wrote: Cool. It didn't occur to me to look for (and through) people's experimental directories. If I were looking for your experimental dir, would I be able to find it in cvs somewhere? Or does it just live in your sandbox on your machine? thank you, crh Daniel's experimental dir is at http://cvs.sourceforge.net/viewcvs.py/fink/experimental/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] Re: A suggestion
On Fri, Jul 02, 2004 at 12:55:27PM -0500, Corey Halpin wrote: Daniel E. Macks wrote: Someone on -devel or #fink (perhaps jfm?) has a giant shell pipeline version of this (and that covers a lot of weird corner cases), that I encapsulated as fink-dep-check in my experimental dir. Cool. It didn't occur to me to look for (and through) people's experimental directories. If I were looking for your experimental dir, would I be able to find it in cvs somewhere? Or does it just live in your sandbox on your machine? When fink folks talk about their experimental directories, they usually mean the experimental module in fink's CVS. You can browse at: http://cvs.sourceforge.net/viewcvs.py/fink/experimental/ and check-out using the usual CVS mechanisms or via that web interface. 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
