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:59:36 -0300 [thread overview]
Message-ID: <871vyfph3r.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <1224233468.30790.125.camel@mill.internal.reciva.com> (Phil Blundell's message of "Fri\, 17 Oct 2008 09\:51\:08 +0100")
Phil Blundell <pb@reciva.com> writes:
> On Thu, 2008-10-16 at 17:02 -0300, Otavio Salvador wrote:
>> Koen Kooi <k.kooi@student.utwente.nl> writes:
>>
>> >> Any objections?
>> >
>> > 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.
>
> This seems like an odd point of view. There are various other things
> that the xserver requires for full operation (fonts, video drivers and
> other modules for example), none of which are listed in RDEPENDS. It
> isn't obvious to me that hal is any more important than those.
Point taken!
Yes your argument changed my mind and I support the removal. This
looks more logical to use same criterion for those packages.
+1
--
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."
next prev parent reply other threads:[~2008-10-17 12:02 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
2008-10-17 8:51 ` Phil Blundell
2008-10-17 11:59 ` Otavio Salvador [this message]
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=871vyfph3r.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