1 |
On Wednesday 16 January 2008, Nikola Zivkovic wrote: |
2 |
> On Wednesday 16 January 2008 07:32:32 pm Caleb Cushing wrote: |
3 |
> > On Thursday 17 January 2008 08:42:16 pm Nikola Zivkovic wrote: |
4 |
> > > 2. Use paludis as default PM. |
5 |
> > |
6 |
> > no. reason... although I haven't tested it recently |
7 |
> > |
8 |
> > 1.) the last 2 times I tried it didn't work out of the box... it asked |
9 |
> > for a config file... all programs should work (maybe not precisely the |
10 |
> > way you want) out of the box. even apache and postfix can be started out |
11 |
> > of the box. |
12 |
> > |
13 |
> > 2.) it's syntax is different. I don't want a new user interface... a new |
14 |
> > backend would be fine. I think most users and admins would agree don't |
15 |
> > change the interface unless it bring significant benefit. |
16 |
> > |
17 |
> > 3.) it's not completely backwards compatible and could potentially break |
18 |
> > things. developers may not care about this but system administrators do. |
19 |
> > |
20 |
> > 4.) it's not done. get it to 1.0 and stable before asking it to replace |
21 |
> > something. |
22 |
> |
23 |
> Naturally I meant to include it when it was finished. |
24 |
> I am using 0.26... and it works very well. It is MUCH faster than emerge, |
25 |
> the config scheme is cleaner and better organized IMHO, and the ooutput it |
26 |
> provides in the console seems much cleaner to me. |
27 |
> It doesn't work out of the box because you have to configure it. The |
28 |
> configuration is relatively easy... especially if you use |
29 |
> portage2paludis.bash. |
30 |
> It hasn't broken anything for me and I've remerged world, gcc, system, |
31 |
> security, etc. However when I used portage to remerge world for 3 days my |
32 |
> machine kept crashing afterwards. |
33 |
> I however hope that *if* paludis manages to win more users over from |
34 |
> portage that it will be included as the default PM. |
35 |
|
36 |
unfortunately, the driving reason for it not being default/supported PM is not |
37 |
technical, but the developer behind it. |
38 |
-mike |