1 |
On Monday 03 October 2005 12:47 am, Ciaran McCreesh wrote: |
2 |
> On Sun, 02 Oct 2005 21:50:07 -0400 Dave Nebinger <dnebinger@××××.com> |
3 |
> |
4 |
> wrote: |
5 |
> | Their build system suits their purpose - distribute a LAMP-like |
6 |
> | system for the foundation of their web application. I'm sure it will |
7 |
> | keep them from getting distracted from questions like 'zimbra works |
8 |
> | for postfix 2.2 but breaks for 2.2.3'; they provide it all and to use |
9 |
> | it you're normally stuck with their 3rd party binaries at the |
10 |
> | version/patch level they give you. |
11 |
> |
12 |
> Hrm. Does this really need an ebuild? |
13 |
|
14 |
I think so. As a stand-alone package it has a number of dependencies that |
15 |
need to be managed, something Portage handles quite well. |
16 |
|
17 |
Also, I'm finding that at it's core, portage handles the reorganization of a |
18 |
distribution quite nicely. Being able to automagically handle the java |
19 |
dependencies using java-pkg is a godsend. Itematically choosing the |
20 |
individual files from the distribution build and retargeting them |
21 |
to /usr/share/webapp with a one-line command... The advantages appear to |
22 |
outweigh the costs. |
23 |
|
24 |
> Wouldn't it be better to use the |
25 |
> associated portage-provided packages? |
26 |
|
27 |
That's the goal - strip out the parts from their distribution that have |
28 |
exiting components already within the portage tree (and already installed on |
29 |
my system). Boils down to a couple of wars for the most part, plus scripts, |
30 |
things like that. |
31 |
|
32 |
> Also, how do you intend to handle |
33 |
> security updates? |
34 |
|
35 |
For the most part I'd leave that to Portage for the 3rd party components. I'm |
36 |
expecting that once I get the initial ebuild figured out, when they release a |
37 |
new distribution I'll just have to re-diff & re-patch if the current patches |
38 |
stop working. |
39 |
|
40 |
> | > | a /var/db/pkg query system, |
41 |
> | > |
42 |
> | > Yick! Bad bad bad idea. |
43 |
> | |
44 |
> | Yeah, I know. But how else do you answer the question "Hey, Portage, |
45 |
> | where did you really install that my.cnf file?" |
46 |
> | |
47 |
> | Obviously the system admin is free to move the my.cnf file or even |
48 |
> | use a different file/path altogether. But at least it would give me |
49 |
> | a starting value to use at compile time... |
50 |
> |
51 |
> I'm starting to think you really shouldn't be ebuilding this lot at |
52 |
> all... |
53 |
|
54 |
I understand your doubts, and trust me I have them to. But the way I see it I |
55 |
have two basic choices: |
56 |
|
57 |
1. use their distribution. This discards all of the advantages that portage |
58 |
provides (i.e. updates to the foundation software). Also means that for each |
59 |
component in their system that is already on mine, I need to shut mine |
60 |
down/unmerge them so the system will rely upon theirs. Will really mess up |
61 |
things like openldap and mysql dependent projects as their distribution |
62 |
doesn't provide the full development stuff portage would need to handle |
63 |
builds. |
64 |
|
65 |
2. create an ebuild to merge only the necessary components into my system, |
66 |
taking advantage of the fact that I already have working components |
67 |
installed. |
68 |
|
69 |
It would seem to me that #2 is the appropriate gentoo-way... |
70 |
|
71 |
I started working on this because I was initially looking for a good web mail |
72 |
package to use on my gentoo box (I'm starting a new contract where I won't |
73 |
have pop3/imap access to my email from the job site). Scope soon creeped to |
74 |
become a good collaboration suite to use on my gentoo box (because I'd have |
75 |
calendars, address books, etc. scattered across many different sources). |
76 |
|
77 |
While I was checking out the options that were already in portage I was also |
78 |
checking online for other possiblilities. The recent posting to slashdot on |
79 |
the very subject caught my eye, and when I went through the flash demo at |
80 |
http://www.zimbra.com I was really impressed with everything I saw. |
81 |
|
82 |
But to get it up and running I soon discovered I'd have to make one of the |
83 |
choices from above. Eventually some 1,000 year old geezer might say "He |
84 |
chose poorly," but who knows - it might work and might catch on. |
85 |
-- |
86 |
gentoo-dev@g.o mailing list |