All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH 1/1] angstrom-2008.1.conf: add PREFERRED_PROVIDER_virtual/psplash -silence warning during parsing
Date: Mon, 30 Mar 2009 17:55:06 +0200	[thread overview]
Message-ID: <gqqq0q$or5$1@ger.gmane.org> (raw)
In-Reply-To: <87wsa72ffd.fsf@neumann.lab.ossystems.com.br>

On 30-03-09 17:33, Otavio Salvador wrote:
> Koen Kooi<k.kooi@student.utwente.nl>  writes:
>
>> On 30-03-09 13:47, Otavio Salvador wrote:
>>> Koen Kooi<k.kooi@student.utwente.nl>   writes:
>>>
>>>> On 26-03-09 01:10, Andrea Adami wrote:
>>>>
>>>>> +#Silence warning during parsing
>>>>> +PREFERRED_PROVIDER_virtual/psplash ?= "psplash-angstrom"
>>>>
>>>> NACK, the 'psplash' package should get deleted and replaced with
>>>> psplash-oe' or something. It was left in place to give people time to
>>>> switch to the new way of installing branded psplash images.
>>>
>>> Hello Koen but I belive those are two different issues.
>>
>>> I added the virtual/psplash package to allow others to properly depends
>>> on an alternative. Currently the only recipe using it is
>>> initramfs-module-psplash but others may come.
>>
>> I don't think virtual/psplash is the way to go, but I don't have a
>> better suggestion.
>
> So what we should do? IMO if there's no better solution we use this
> until we find one.
>
>>> I fully agree that we should drop plain psplash recipe and have
>>> people to use the branded one but I also think angstrom needs to
>>> properly set the preferred version since it will then allow that
>>> its users to use it without much hassle.
>>
>> Unfortunately this will end up with people spreading FUD like "can't
>> change psplash logo in angstrom" just because they see that line in
>> angstrom.conf.
>
> Well, we could add a comment for that in the angstrom.conf file.
>
> Something like:
>
> # This enforces a specific brand to be used, in our case the angstrom
> # one. In case you want to change the logo or something like that we
> # suggest you to create another recipe (e.g: psplash-<brand>) for that
> # and change this line according.
> PREFERRED_VERSION_...

Maybe

# This enforces a specific brand to be used, in our case the angstrom
# one. In case you want to change the logo or something like that we
# suggest you to create another recipe (e.g: psplash-<brand>) for that
# and add that into your image.
# You can also opt to change or override this line, but that isn't
# needed because psplash is using update-alternatives.

regards,

Koen




  reply	other threads:[~2009-03-30 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1238025789.git.andrea.adami@gmail.com>
2009-03-26  0:10 ` [PATCH 1/1] angstrom-2008.1.conf: add PREFERRED_PROVIDER_virtual/psplash -silence warning during parsing Andrea Adami
2009-03-26  0:25   ` Andrea Adami
2009-03-26  7:51   ` Koen Kooi
2009-03-30 11:47     ` Otavio Salvador
2009-03-30 12:07       ` Koen Kooi
2009-03-30 15:33         ` Otavio Salvador
2009-03-30 15:55           ` Koen Kooi [this message]
2009-03-31 23:45             ` [PATCH] angstrom-2008.1.conf: add PREFERRED_VERSION_psplash Andrea Adami
2009-04-01  7:50               ` Koen Kooi
2009-04-01 13:30                 ` Andrea Adami
2009-03-30 17:02         ` [PATCH 1/1] angstrom-2008.1.conf: add PREFERRED_PROVIDER_virtual/psplash -silence warning during parsing Michael 'Mickey' Lauer
2009-03-30 17:34           ` Philip Balister

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='gqqq0q$or5$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.