From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: X/Qt2 opie integration (patches included)
Date: Tue, 07 Oct 2008 13:47:19 +0200 [thread overview]
Message-ID: <gcfi87$g4t$1@ger.gmane.org> (raw)
In-Reply-To: <48EB45F0.8080809@opensimpad.org>
On 07-10-2008 13:20, Bernhard Guillon wrote:
> Any obstacles left? Else I would like to ask if some of you can please
> commit it [2] [3] to .dev branch.
I still dislike a single package handling so many different things *and*
containing config files for other packages.
> best regards
> Bernhard Guillon
>
> 1 http://linuxtogo.org/gowiki/Angstrom/XQt/playground
> 2 http://bugs.openembedded.net/show_bug.cgi?id=4582
> 3 http://bugs.openembedded.net/show_bug.cgi?id=4603
>
> Bernhard Guillon schrieb:
>> Koen Kooi schrieb:
>>>
>>> NACK!
>>>
>>> +do_install() {
>>> [..]
>>> + install -d ${D}/home/root
>>> + install -m 0600 .blackboxrc ${D}/home/root
>>>
>>> A package NEVER EVER touches $HOME. NEVER! I wish ascii could
>>> produces some bigger capitals that blink and have baseballbats to get
>>> the point across, but sadly it can't.
>>>
>>> Imagine I don't log in as root and fire up packagekit to install that
>>> packages. I don't get the .blackboxrc, but the root user suddenly has
>>> his .blackboxrc overwritten without notice.
>>>
>>> So:
>>>
>>> A package NEVER EVER touches $HOME. NEVER!
>>>
>>> ${sysconfdir} exists for a reason.
>>>
>> Ok, I added a second version of the patch to the bugtracker which
>> implements your suggestion.
>>
>> I did use ${HOME} in the first version because it is the standard
>> location for blackbox configuration [1].
>>
>> Is there any way for a clean implementation to put the config to the
>> standard location? With e.g postinstall? I don't like the idea of not
>> using a standard location but I agree that hardcode to /home/root can
>> cause trouble.
>>
>>
>> best regards
>> Bernhard Guillon
>>
>> 1
>> http://blackboxwm.sourceforge.net/BlackboxDocumentation/BlackboxConfiguration#location
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2008-10-07 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 18:19 X/Qt2 opie integration (patches included) Bernhard Guillon
2008-10-04 6:30 ` Koen Kooi
2008-10-04 11:51 ` Bernhard Guillon
2008-10-07 11:20 ` Bernhard Guillon
2008-10-07 11:47 ` Koen Kooi [this message]
2008-10-07 12:33 ` Bernhard Guillon
2008-10-07 12:43 ` Koen Kooi
2008-11-21 17:32 ` Bernhard Guillon
2008-11-23 10:06 ` Bernhard Guillon
2008-10-07 12:43 ` Graeme Gregory
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='gcfi87$g4t$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox