Op 6 mei 2011, om 16:51 heeft Koen Kooi het volgende geschreven:
>
> Op 6 mei 2011, om 16:20 heeft Richard Purdie het volgende geschreven:
>
>> On Fri, 2011-05-06 at 15:39 +0200, Koen Kooi wrote:
>>> Now onto my issues:
>>>
>>> packaging:
>>> In OE .dev I added FILES_${PN} += "${base_libdi
On Fri, May 6, 2011 at 13:06, Koen Kooi wrote:
>
> Op 6 mei 2011, om 17:36 heeft Otavio Salvador het volgende geschreven:
>
>> On Fri, May 6, 2011 at 11:51, Koen Kooi wrote:
>>> So, is having both sets inside ${PN} a dealbreaker?
>>
>> I think it is not BUT this choice could be a distro choice.
>
Op 6 mei 2011, om 17:36 heeft Otavio Salvador het volgende geschreven:
> On Fri, May 6, 2011 at 11:51, Koen Kooi wrote:
>> So, is having both sets inside ${PN} a dealbreaker?
>
> I think it is not BUT this choice could be a distro choice.
Everything can be a distro choice, you can make gtk/qt
On Fri, May 6, 2011 at 11:51, Koen Kooi wrote:
> So, is having both sets inside ${PN} a dealbreaker?
I think it is not BUT this choice could be a distro choice. So I see as:
USE_INIT=(sysv|systemd|both)
Being both the default.
--
Otavio Salvador O.S. Systems
E-mail
Op 6 mei 2011, om 16:20 heeft Richard Purdie het volgende geschreven:
> On Fri, 2011-05-06 at 15:39 +0200, Koen Kooi wrote:
>> Now onto my issues:
>>
>> packaging:
>> In OE .dev I added FILES_${PN} += "${base_libdir}/systemd" to udev,
>> dbus, rsyslog and avahi. This means we end up with bo
On Fri, May 06, 2011 at 04:32:08PM +0200, Koen Kooi wrote:
>
> Op 6 mei 2011, om 15:54 heeft Martin Jansa het volgende geschreven:
>
> > On Fri, May 06, 2011 at 06:51:58AM -0700, Chris Larson wrote:
> >> On Fri, May 6, 2011 at 6:39 AM, Koen Kooi
> >> wrote:
> >>> And related to this: how do I g
Op 6 mei 2011, om 15:54 heeft Martin Jansa het volgende geschreven:
> On Fri, May 06, 2011 at 06:51:58AM -0700, Chris Larson wrote:
>> On Fri, May 6, 2011 at 6:39 AM, Koen Kooi wrote:
>>> And related to this: how do I get the "installed but not packaged" output
>>> back? The bitbake logging cha
On Fri, 2011-05-06 at 15:39 +0200, Koen Kooi wrote:
> Now onto my issues:
>
> packaging:
> In OE .dev I added FILES_${PN} += "${base_libdir}/systemd" to udev,
> dbus, rsyslog and avahi. This means we end up with both sysV script
> and systemd units. What I would like to have is ${PN}-sysvini
On 5/6/11 8:39 AM, Koen Kooi wrote:
> Hi,
>
> The past few days I have gotten systemd to work in OE.dev and I have some
> questions on how to do in the oe-core universe. First some background:
>
> Systemd is a /sbin/init replacement using ideas from apples launchd like
> socket activation. Star
On Fri, May 06, 2011 at 06:51:58AM -0700, Chris Larson wrote:
> On Fri, May 6, 2011 at 6:39 AM, Koen Kooi wrote:
> > And related to this: how do I get the "installed but not packaged" output
> > back? The bitbake logging changes are hiding it now, which is
> > counterproductive.
>
> Could chang
On Fri, May 6, 2011 at 6:39 AM, Koen Kooi wrote:
> And related to this: how do I get the "installed but not packaged" output
> back? The bitbake logging changes are hiding it now, which is
> counterproductive.
Could change those messages from info to warnings, then they'd show up.
--
Christoph
Hi,
The past few days I have gotten systemd to work in OE.dev and I have some
questions on how to do in the oe-core universe. First some background:
Systemd is a /sbin/init replacement using ideas from apples launchd like socket
activation. Startup scripts are replaced by .ini like files:
sshd
12 matches
Mail list logo
