Re: [Fink-devel] Stopping Spotlight
So we're going to try moving the default buildpath from %p/src to %p/ src/fink.build. Will this be %p/src/foo-%v-%r.build or %p/src/fink.build/foo-%v-%r? And what will happen to the install (%p/src/root-*) directories? Will they also be nested into the %p/src/fink.build/ directory? I'm mostly just thinking that doing %p/src/fink.build/everythinghappensinhere just leads to an extra directory nest when all that seems to be needed from the description is appending .build to the build and install directories. Hanspeter -- Hanspeter Niederstrasser, Ph.D.Dept. of Cell Biology hniederstrasser at cellbiology.wustl.edu Campus Box 8228 Cooper Lab 660 South Euclid Avenue Washington University in St. Louis St. Louis, MO 63110 --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402alloc_id=16135op=click ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Stopping Spotlight
On 25 May 2005, at 04:49, Dave Vasilevsky wrote: If you have a custom build path, Fink will warn you that this might be slowing down your builds, and offer to append .build--if you decline, Fink will never bother you about it again. I declined _ since I have spotlight turned off _, but I've been asked this question already half a dozen times _ at least at every fink index, selfupdate, list, ... command. Jean-François --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_idt02alloc_id135op=click ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Stopping Spotlight
On 25 May 2005, at 16:00, Jean-François Mertens wrote: On 25 May 2005, at 04:49, Dave Vasilevsky wrote: If you have a custom build path, Fink will warn you that this might be slowing down your builds, and offer to append .build--if you decline, Fink will never bother you about it again. I declined _ since I have spotlight turned off _, but I've been asked this question already half a dozen times _ at least at every fink index, selfupdate, list, ... command. In addition, this breaks the simplests scripts; eg: #!/sw/bin/bash ls=`fink dumpinfo -f family $1` echo $ls hangs... JF --- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_idt02alloc_id135op=click ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Stopping Spotlight
On May 25, 2005, at 9:55 AM, Hanspeter Niederstrasser wrote: Will this be %p/src/foo-%v-%r.build or %p/src/fink.build/foo-%v-%r? The second one. Packages will build in %p/src/fink.build/%f and will install in %p/src/fink.build/root-%f . I'm mostly just thinking that doing %p/src/fink.build/ everythinghappensinhere just leads to an extra directory nest when all that seems to be needed from the description is appending .build to the build and install directories. We considered appending .build to the subdirectories like this. However, some packages may expect to build in a directory named %f and could break. On the other hand, Buildpath is known to be relocatable already, so this seemed to be the safer solution. Dave PGP.sig Description: This is a digitally signed message part
[Fink-devel] Stopping Spotlight
Hi folks, Some of you have already noticed Spotlight indexing /sw/src, which makes builds slow. For various reasons the solutions suggested so far aren't ideal[1], but msachs found out for us that directories with the *.build do not have anything inside them indexed. So we're going to try moving the default buildpath from %p/src to %p/ src/fink.build . If we decide to release Fink with this change, those using the default buildpath will use the new one automatically. If you have a custom build path, Fink will warn you that this might be slowing down your builds, and offer to append .build--if you decline, Fink will never bother you about it again. I'll be committing the changes to fink HEAD just after sending this. msachs is going to run another complete build, so that should help find any problems. I don't think there are any other situations where fink is badly impacted by Spotlight. I suppose if you do a lot of installing/ removing that could cause problems. The new incremental indexing in HEAD creates lots of files, however that's apparently not a problem so long as there's no mdimporter. But if there are other places where we'd like to disable Spotlight, we've got a reasonable strategy now. Comments would be appreciated. Dave [1] The solutions involved modifying files in /.Spotlight-V100. But Spotlight doesn't notice changes to the relevant files right away, build paths on different volumes are harder to deal with, and munging plists isn't fun. PGP.sig Description: This is a digitally signed message part
