I'm looking at packaging up the latest gEDA tarball (1.6.0), and upstream has moved from one tarball per component to a single tarball for everything including the private libraries.
I can split off the -dev and -shlibs portions easily enough, but I got the feeling from reading the TexLive thread that the Fink dependency engine does things a little differently than native dpkg/apt when it comes to Provides/Replaces. Should I keep around dummy .info files for the auxiliary packages like geda-docs and geda-utils, and have them depend on the new core package and fink-obsolete-packages? -- Charles Lepple ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ 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
