Packaging Omni frameworks for distribution.
Packaging Omni frameworks for distribution.
- Subject: Packaging Omni frameworks for distribution.
- From: Charles Bennett <email@hidden>
- Date: Fri, 06 Jul 2001 10:58:35 -0400
Hi all, My application uses the wonderful omni frameworks for some of the networking
code. I have two questions..
1: How should the target settings be handled for headers? There is no need
for them to go with the installed app. Do I turn off both public and private?
2: What makes the most sense in term of packaging the frameworks for distribution?
Should I bury them inside my app or install them to /Library/Frameworks or just
provide another .pkg with only the frameworks, and explain that you
"may" need to install this package? I'm not worried about developers in the
sense that they "know" what they want to happen. I'm trying to figure out what the
best way to deal with a "user" would be and how this would effect other developers
that want to install the frameworks for their apps as well..
I'm just trying to figure out a method that all developers can use, to stay out
of each others way. It seems to me that if we can all agree on some guidelines
now. Then we will avoid a larger problem later.
Comments?
chuck
Greg Titus wrote:
>
>
> As a consumer of such classes, I would certainly like to see
>
> announcements
>
> on this list. Preface the subject line with [ANN] to attract attention.
>
>
Well, given this ringing endorsement, I'll officially mention our
>
frameworks this once, since it looks like there are a bunch of new
>
people on this list that might not be aware of them. The source is
>
available for the vast majority of The Omni Group's framework code -
>
code which has been used in shipping applications for years now (and not
>
just by us) so it is generally fairly solid. It is distributed with our
>
own BSD-style license: you are free to use the code, including in
>
products you sell for money, and there is no viral component like the
>
GPL. However, the license does keep you from selling our code by itself,
>
and from redistributing modified copies.