Thank you for you response!

On 5/23/08, Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
> On Fri, 23 May 2008 00:56:54 +0300
>
> "Alon Bar-Lev" <[EMAIL PROTECTED]> wrote:
>
> > > It isn't missing any basic features. It's missing some things about
>  > >  which we don't really care.
>  >
>  > Ok...
>  > So let me see if I understand correctly, there is no etc-update,
>
>
> You can use any of the config update tools. For Exherbo, we're using
>  'eselect config'. For Gentoo, carry on using etc-update, or
>  dispatch-conf, or conf-update, or any of the zillion other options.

OK... Although this is essential part of package manager, as you
cannot complete installation without making sure configuration files
are in place. I agree user may choose to use a different
implementation, but a simple tools should be provided.

>  > no binary packages (quickpkg)
>
>  Binaries we will be doing at some point. But they're not an essential
>  feature for what we're doing.

So how do you manage large network with paludis?
You compile from sources at every endpoint?
Say you have 1000 workstations with different applications installed
at large groups, do you expect network admin to compile each package
over and over on all workstations?

I don't understand "essential feature for what we're doing"...
I guess I expect to me being able to find that paludis first provides
the same feature set for users, then made these better... :)

>  > no phases for package developers (ebuild)
> Again, at some point, unless we decide that implementing them will
>  stop developers from fixing their bad development habits. But again,
>  they're not an essential feature nor even particularly useful.

It is great you want to force quality, but I don't understand why you
keep mentioning that this stop developers from doing good job... As I
wrote you in ticket#580, you cannot do good job if you don't verify
the outcome of every phase. This does not mean you don't check the
outcome of the whole process.

At the end you don't provide the tools to enhance the quality.

>  > no cross compile toolchain support.
> For Exherbo we'll be doing cross compiling properly at some point. For
>  Gentoo you can't cross compile reliably anyway...

OK. I will wait and see.

>  > Current configuration for users is to have portage and paludis in
>  > parallel, completing missing functionality from portage tools.
>
>
> Uh... No particular need to have a Portage config anywhere...

Yes I do, as I care about the quality of my ebuilds, I have to
continue use ebuild for checking the phases.
And as I must continue use cross compile, I must continue use crossdev.
And I distribute binary packages from compiler to network, so I need
to use quickpkg.

I thought I can move to paludis to prepare to easy Exherbo migration,
but I don't think I can do this.

Thank you for your help!
Alon.
_______________________________________________
paludis-user mailing list
[email protected]
http://lists.pioto.org/mailman/listinfo/paludis-user

Reply via email to