Re: Becoming the OS X binary maintainer

Hi,

So, a progress report.

I have been reviewing what we have so far in the two macsetup and osxsetup sub-projects (plus a 3.0.16 package that's out there 'in the wild') and there's a lot of great stuff in all three. My intent therefore is to combine the best of these into a new sub-project I provisionally entitle osxbuildsystem.

I have access to a 10.6.8 Intel Macbook Pro and a 10.4.11 PowerBook, so in the fullness of time I *hope to have builds for both Intel & PPC targeting all releases from 10.3 to 10.7. I will use pre/post install scripts to use the appropriate method for creating user/group and installing startup item/launchd plist, and plan to include the Privoxy Utility as an optional item.

A question. Do you think it likely that a single 32 bit Intel build will run equally well on all OS X releases or are there varying dependencies/linkage across versions? Obviously I will walk before I can run, meaning my first goal is to create an install package targeting only 10.6, but it'll be useful to know if that is likely to run directly on other releases.

More as I work on it,

Ian



On 2011-11-28, at 10:00 AM, Fabian Keil wrote:

> David Schmidt <[email protected]> wrote:
> 
>> The main source code will likely still compile without trouble using the 
>> gnu C compiler (there is no Objective-C in the project so far as I 
>> know... at least I never used it while maintaining it).
> 
> I was under the impression the "Privoxy Utility" was written
> in Objective-C but now that I checked it seems to be Applescript.
> 
> main.m appears to be Objective-C, but its purpose isn't
> entirely clear to me.
> 
>>                                                        But of course 
>> putting Privoxy on the Apple app store is a non-starter since it's Open 
>> Source.  A .dmg is probably all that most folks need, anyway.
> 
> My understanding is that Apple's app store doesn't forbid
> Open Source licenses in general, but only the viral and more
> restrictive ones like the GPLs which would force Apple to
> open up things they don't want to.
> 
> The "Privoxy Utility" has a more permissive license (compared
> to the GPLv2), so putting it on the app store by itself might
> not violate Apple's terms of service (which I never read):
> http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/macsetup/Xcode/Privoxy%20Utility/Privoxy%20Utility.applescript?revision=1.2&view=markup
> 
> While the "Privoxy Utility" isn't particular useful without
> Privoxy, putting it on the app store might help to make
> OS X users aware of the fact that Privoxy binaries are
> available again.
> 
> I'm not sure if it would be worth the effort. It could also
> result in a lot of negative "app doesn't work" comments.
> 
> Fabian
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure 
> contains a definitive record of customers, application performance, 
> security threats, fraudulent activity, and more. Splunk takes this 
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d_______________________________________________
> Ijbswa-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ijbswa-developers


------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of 
discussion for anyone considering optimizing the pricing and packaging model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/