On Fri, Sep 22, 2006 at 07:35:33PM +0100, Alex Smith <[EMAIL PROTECTED]> wrote: > 1 and 2) The solution would be to create a init-mess repo (like crazy's > dbus-mess ;P) > and get every package that has an initscript and port it. I can easily do > this myself.
okay, we'll see how will this work out :) i mean i think dbus-mess, python25 and init-mess repos will conflict each other > 3) Yes, but it would be 2 teams working on it - i'm not good with gui > programming in C, > i'm better at lower-level stuff. So I could work on init, while krix, desco > and others > work on gfpm. ok, if we decide we want to write something new then feel free to start working on it, then worst is to talk about it and doing nothing :) > I personally think it would be a good idea to have an initscripts package for > whatever > system we choose, and have initscripts for every package in it. That way it > would be > easier to maintain - make a global initscript change without having to > rebuild every > package that's not so good imho. in that case if a new package would require an initscript, we would need to bump the initscripts package. see, /etc/group provides only a few groups, most group is added by post_install scripts. the init scripts should be provided by the packages udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org _______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
