Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@debian.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: xserver-xorg rdepends
Date: Fri, 17 Oct 2008 08:54:13 -0300	[thread overview]
Message-ID: <87ej2fphcq.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <gd87ga$b9n$1@ger.gmane.org> (Koen Kooi's message of "Thu\, 16 Oct 2008 22\:17\:14 +0200")

Koen Kooi <k.kooi@student.utwente.nl> writes:

>>> Yes. Recent xservers need hal for various input systems to work
>>> correctly. So instead of crippling the xserver you can keep a crippled
>>> version in your personal tree or overlay.
>>
>> Fully support to keep hal as rdepends.
>
> Thinking about it some more, we should turn back the libhal split, so
> every hal apps works, instead of adding rdepends when we encounter
> broken apps.

Personally I disagree with you. Even though few applications can still
not work without the hal rdepends, some uses hal but not in a really
non dependant way and the split allows a finner selection where to
include or not it.

This allows also distros to select and change it by package.

> PS: how can I merge your xfce work into .dev? The git phrasebook isn't
> really clear on that.

I'm rebasing the branch against final repository and I'll send a
patchset for acking here before pushing it. I guess I can send those
patches later today and push it tomorrow if someone acks it before
that.

My idea is to split the patches in:

 - xfce-refactor-branch

   where the inc files are droped and the packaging improved

 - xfce-4.2-branch

   new version

There're also a number of fixes that I'll be sending here for review
and pushing together. 

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
 you the whole house."



  reply	other threads:[~2008-10-17 11:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 19:19 xserver-xorg rdepends Phil Blundell
2008-10-16 19:53 ` Koen Kooi
2008-10-16 20:02   ` Otavio Salvador
2008-10-16 20:17     ` Koen Kooi
2008-10-17 11:54       ` Otavio Salvador [this message]
2008-10-17  8:51     ` Phil Blundell
2008-10-17 11:59       ` Otavio Salvador
2008-10-17 15:55       ` Michael 'Mickey' Lauer
2008-10-17 17:09         ` Koen Kooi
2008-10-17 18:05           ` Michael 'Mickey' Lauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ej2fphcq.fsf@neumann.lab.ossystems.com.br \
    --to=otavio@debian.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox