On Wed, Oct 26, 2011 at 03:17:01PM +0200, Michal Soltys wrote: [...]
Btw, shouldn't we try to add application specific stuff like the one for lvm and mdadm via the corresponding port, a kind of run-control directory with short scripts added by the packages comes to my mind?
I'd rather left that to users. More complex configurations can vary quite a lot, their parts can be stuffed in different places - depending on one's needs. Existing hooks are just an example/headstart.
Hmm, sorry, but my point was a different one. The only, or at least biggest, problem I see with our current rc stuff is the missing feature to extend/modify it via our packages. And that's nothing we can left over to the user, but the packager of the concerned port has to do. [1] is a good example for such an extension, my idea for a nice solution would be to add code to the init system via the mdadm package and not to hardcode it to rc. Maybe something similar what you can do with udev rules or with cron by adding stuff to the /ect/cron.d directory. [...]
I started updating pkgmk as well, I can't live without native git support, and few lesser things (such as local directories) ... for a start ;)
I don't see why we need native git support in pkgmk. I'd suggest to go the usual way and discuss the problems and ideas first here and start coding after a common decision, not the other way around ;) Don't get me wrong, every help for CRUX is much appreciated, but with our very limited resources we should use them in the most effective and prioritized way, IMHO.
Maybe add regular crux@ to CC as well ?
Why? I think crux-devel is the appropriate place for such discussions. best regards Juergen [1] http://crux.nu/bugs/index.php?do=details&task_id=747