All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Guillon <Bernhard.Guillon@opensimpad.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: X/Qt2 opie integration (patches included)
Date: Sat, 04 Oct 2008 13:51:39 +0200	[thread overview]
Message-ID: <48E758CB.7040209@opensimpad.org> (raw)
In-Reply-To: <gc72hu$i8f$1@ger.gmane.org>

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



  reply	other threads:[~2008-10-04 11:56 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 [this message]
2008-10-07 11:20     ` Bernhard Guillon
2008-10-07 11:47       ` Koen Kooi
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=48E758CB.7040209@opensimpad.org \
    --to=bernhard.guillon@opensimpad.org \
    --cc=openembedded-devel@lists.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.