On Sun, 02 Oct 2005 20:48:27 -0400 Dave Nebinger <[EMAIL PROTECTED]> wrote: | So yeah, things are pretty complicated due to the upstream build | system expectations.
I suggest hitting upstream with a cluebat until they make a proper build system. | 1. Can I use /usr/local/portage/eclass for development/testing? Portage is kinda broken with eclasses in overlay... It'll work, so long as you remember to touch all affected ebuilds every time you change the eclass. | 2. Do I create a single eclass, i.e. zimbra.eclass, to represent an | eclass for a specific package or do I generate multiple eclasses | based upon functionality? Well... If it's really an eclass for a whole package, it may not be worth packaging the thing at all. | a /var/db/pkg query system, Yick! Bad bad bad idea. | 3. Do eclasses get submitted on the same bug report as the ebuild | submission, or do they get a bug report of their own? All in one bug's usually easier. -- Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm
pgpTzLowWrmPd.pgp
Description: PGP signature
