On Jun 12, 2008, at 1:10 PM, ted bonkenburg wrote: > On Thu, Jun 12, 2008 at 8:33 AM, Dave Koziol <[EMAIL PROTECTED]> > wrote: >> Offtopic: I'm curious what Missing Sync for Windows Mobile is using >> MacFUSE for.
Missing Sync for Windows Mobile uses MacFUSE to allow access to the file systems on the device directly to the end users. The device and any storage cards in the device are mounted as volumes. > I've seen the PackageMaker issue with at least one other product aside > from ExpanDrive. It seems that PackageMaker will re-write the bundle > identifier and version string as well as remove whatever was in the > Resources directory when you drag a .pkg into the interface. Please > double-check the MacFUSE Core.pkg in your created .mpkg to make sure > that this isn't happening to you as well. > > I've been told that this problem does not seem to occur if you use > Iceberg to create .mpkgs. We build our meta packages via scripts instead of via any tools, so no modification should be happening to the MacFUSE package. >> Our only "issue" with the Package as currently distributed is that >> the >> info.plist file contains a IFPkgFlagInstalledSize with a size of 0. >> This results in a less than ideal experience and we currently work >> around this by removing that key from the Info.plist file. But we'd >> like to see the next release of MacFUSE built in such a way that this >> is no longer required by us. > > Can you describe what the less than ideal experience is? Is it simply > that it doesn't tell you in advance the estimate of how much disk > space it'll take up or is there something else that I'm missing? It > looks like if I remove the key from the Info.plist.in that is used to > generate the "MacFUSE Core.pkg" then it will be created and filled in > properly by packagemaker. I'm happy to get that change in for the next > release if it solves your issue. The less than ideal experience is that MacFUSE will show up as requiring 0K on disk in the customize installer packages view instead of the actual required size. If we remove this key, Installer.app calculates the size, and everything works nicely. > In the future, please don't hesitate to let us know about such issues. > I won't guarantee that we'll fix things, and we might disagree about > what needs fixing or how things should be changed, but if we don't > even *know* that you are having a problem then it doesn't help > anything. And yes, I would have reported it sooner if I'd have known we did this soon, but the person who made the change didn't tell me until recently... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to macfuse-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse-devel?hl=en -~----------~----~----~----~------~----~------~--~---
