On 05/09/2009, at 03:34, Saadat wrote: > I would like to make the application available through fink, i.e. > "fink > install myapp" should work.
As I said before (and now with pointers to further information), you may: a) Submit a package description to Fink. If it conforms to Fink's policy it will eventually be part of Fink's distribution and users will be able to install it in the same manner they already do with other packages. b) Provide a package description file (.info, and .patch if necessary) and ask users to install it on their local tree [1]. This will allow users to build it from source and install it. You'll need to set up some mechanism so that users get updates of your package description file. c) Provide both a package description file, and binary .deb packages for the combinations of architecture and OS X version of your user base. When users run 'fink install yourpkg' it won't be built from source as it's already available as a binary package. The binary .deb packages must be available via an APT repository you'd need to set up. Ask users to install the package description on their local tree [1] and configure their installations to use your APT repository [2]. You'll also need to set up some mechanism so that users get updates of your package description file. [1] http://finkers.wordpress.com/2009/06/08/local-packages/ [2] http://finkers.wordpress.com/2009/06/01/fink-and-binary-distributions/ As you may see, the first option seems to be the simplest. I also know of one university department that was willing to set up their own restricted, local APT repository for their students but I'm not sure if they ended up doing this. Another university, Tokyo U., decided to submit (a subset of?) their packages to Fink and provide an APT repository that can be used by every Fink user. > My application uses components, which have GPL2, GPL, BSD and MIT > licenses. > Looking at the packaging instructions, it seems that I would have to > have > one license under which the application is released. If I cannot > resolve the > license issues to the satisfaction of the Fink distribution approval > process, I was thinking that I could just release the binary > distribution > for now and release the source distribution after verifying the > license > stuff. As Martin's already said, you may use the umbrella OSI-Approved licence if every licence is in fact approved by OSI [3]. On the other hand, can't these components be separate packages? If they're libraries we prefer they're packaged separately. That helps with licencing (using a more specific licence rather than OSI-approved), upgrading (users won't have to rebuild the whole package if there's only been a change in one of the libraries), and reuse (other packages that want to use that library can just reuse the one that's already installed). [3] http://www.opensource.org/licenses/alphabetical > On Fri, Sep 4, 2009 at 6:03 PM, monipol <[email protected]> wrote: > >> On 04/09/2009, at 21:11, Saadat wrote: >> >>> I am looking for information on how to properly build and deploy a >>> binary >>> package using fink. I've looked at the documentation and the FAQs, >>> but am >>> still unsure of what constitutes a good fink binary package. >>> >> >> Fink provides the infrastructure for building packages from source >> and >> installing binary packages via Debian-based (dpkg, APT) tools. >> Usually >> maintainers submit package descriptions -- which contain >> instructions on how >> to fetch source code, build it, install it -- that are incorporated >> into >> Fink's distribution after approval. >> >> I'm not sure I understand your request correctly. Do you want to >> provide a >> binary package that can be installed via Fink but is not present in >> Fink's >> distributions? If so, you need to write a package description and >> make sure >> that every dependency is available either in Fink or by your own >> means. You >> would also need to provide binary packages for every combination of >> architecture (ppc, i386, x86_64) and most possibly operating system >> version >> (OS X 10.4, 10.5, 10.6) you want to support. You would also need to >> give >> users specific instructions on how to install this package of yours >> because >> it won't be readily available as other packages present in Fink's >> distributions. >> >> Note that if you write a package description and submit it to Fink >> then it >> might (after validation) be part of Fink itself, relieving you from >> the >> burden of providing specific instructions on how to install your >> package and >> making it available to other users. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fink-devel mailing list [email protected] http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
