1 |
On Sunday 02 October 2005 09:28 pm, Ciaran McCreesh wrote: |
2 |
> On Sun, 02 Oct 2005 20:48:27 -0400 Dave Nebinger <dnebinger@××××.com> |
3 |
> |
4 |
> wrote: |
5 |
> | So yeah, things are pretty complicated due to the upstream build |
6 |
> | system expectations. |
7 |
> |
8 |
> I suggest hitting upstream with a cluebat until they make a proper |
9 |
> build system. |
10 |
|
11 |
Their build system suits their purpose - distribute a LAMP-like system for the |
12 |
foundation of their web application. I'm sure it will keep them from getting |
13 |
distracted from questions like 'zimbra works for postfix 2.2 but breaks for |
14 |
2.2.3'; they provide it all and to use it you're normally stuck with their |
15 |
3rd party binaries at the version/patch level they give you. |
16 |
|
17 |
So no matter how hard or how long I was going to hit them with the cluebat, |
18 |
they're not going to bend. |
19 |
|
20 |
Their distribution is structured as follows: |
21 |
/opt/zimbra |
22 |
/opt/zimbra/bin |
23 |
/opt/zimbra/conf |
24 |
... |
25 |
/opt/zimbra/postfix |
26 |
/opt/zimbra/postfix/bin |
27 |
/opt/zimbra/postfix/etc |
28 |
... |
29 |
/opt/zimbra/tomcat |
30 |
/opt/zimbra/tomcat/bin |
31 |
/opt/zimbra/tomcat/conf |
32 |
... |
33 |
|
34 |
Yada yada yada. The alterations to get it to fit under a regular distribution |
35 |
make the resulting ebuild pretty large. |
36 |
|
37 |
All for the goal of extracting two web applications and some configuration |
38 |
info. Go figure. |
39 |
|
40 |
> | 2. Do I create a single eclass, i.e. zimbra.eclass, to represent an |
41 |
> | eclass for a specific package or do I generate multiple eclasses |
42 |
> | based upon functionality? |
43 |
> |
44 |
> Well... If it's really an eclass for a whole package, it may not be |
45 |
> worth packaging the thing at all. |
46 |
|
47 |
That's the rub. Create eclass(es) to make a single ebuild less complex, or |
48 |
skip the eclasses and have a larger ebuild. |
49 |
|
50 |
> | a /var/db/pkg query system, |
51 |
> |
52 |
> Yick! Bad bad bad idea. |
53 |
|
54 |
Yeah, I know. But how else do you answer the question "Hey, Portage, where |
55 |
did you really install that my.cnf file?" |
56 |
|
57 |
Obviously the system admin is free to move the my.cnf file or even use a |
58 |
different file/path altogether. But at least it would give me a starting |
59 |
value to use at compile time... |
60 |
-- |
61 |
gentoo-dev@g.o mailing list |