On Tue, 5 Feb 2008 12:53:01 -0500 (EST)
"Benjamin R. Haskell" <[EMAIL PROTECTED]> wrote:
> But, is there a good summary somewhere of why Paludis and webapps
> don't mix well? I have to test some things with cakephp, but if
> there's a larger problem I could contribute to solving while having
> to do that, that'd be better use of my time. If no one has a succinct
> explanation, I'll start poking around on my own, but again, figured
> I'd ask.

Basically... Stuart's design goals for webapp-config were bizarre and
completely at odds with what most people want. He wanted it to work on
any distribution, and so not be too tied to the ebuild format. He also
wanted it to work on Windows, and so not be too tied to Unix either. He
wanted it to be a tool used by people who manage a webserver with
multiple independent users with shell accounts, as a way of installing
webapps for those users without letting the users themselves run
scripts.

In order to do this, he essentially created a second domain-specific
package manager, and a rather lousy one at that. In order to make it
more or less look like it's part of Portage, he then added a load of
messy glue code that ties webapps to emerge to webapps. This glue
doesn't work properly even with Portage, let alone other package
managers...

Honestly, if you're looking to manage webapps, you're better off
managing them by hand.

-- 
Ciaran McCreesh

Attachment: signature.asc
Description: PGP signature

_______________________________________________
paludis-user mailing list
[email protected]
http://lists.pioto.org/mailman/listinfo/paludis-user

Reply via email to