On Wed, Aug 24, 2011 at 04:57:31PM +0200, Steffen Sledz wrote:
> On 24.08.2011 16:45, Martin Jansa wrote:
> > On Wed, Aug 24, 2011 at 04:34:06PM +0200, Steffen Sledz wrote:
> >> On 24.08.2011 14:36, Marcin Juszkiewicz wrote:
> >>> W dniu 24.08.2011 14:31, Steffen Sledz pisze:
> >>>> BTW: What is the exact meaning/purpose/use of task-proper-tools?
> >>> 
> >>> Replace busybox components by full versions. Was made years ago and then updated by several people. While working for BugLabs company I used it to create rootfs without busybox.
> >>> 
> >>>> The list contains a lot of tools with existing alternatives (e.g. syslog-ng vs. rsyslog or pump vs. dhcpcd).
> >>> 
> >>> Then propose change which will allow to install one of them only at time?
> >> 
> >> Sorry, but my knowledge is not sufficient to do this. I've no idea how to reference u-a related tools here.
> > 
> > Why you don't remove task-proper-tools from your images RDEPENDS and add only tools you need which aren't provided by upstart?
> 
> task-proper-tools is not directly in our image RDEPENDS but inherited via task-sdk-native (may be via others too).

then maybe it's time to propose removing it from task-sdk-native or add
switch controlling if it should be included or not.

> > or use something like DISTRO_SYSLOG ?= "syslog-ng" in task-proper-tools
> > 
> > and set DISTRO_SYSLOG = upstart for your distro if distro level granularity is fine for you (all supported images are using upstart).
> 
> We do not have an own distro (we use angstrom). It's only a custom image.
> 
> And the initial problem is sysvinit vs. upstart which are not u-a but need to be installed exclusively. If i'm right this is done by setting IMAGE_INIT_MANAGER. Can this variable used inside the task-proper-tools RDEPENDS?

No because you have one global task-proper-tools for different images
(with possible different IMAGE_INIT_MANAGER values).

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com