All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro del Castillo <alejandro.delcastillo@ni.com>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] lib/oe/rootfs: Fix DEBUGFS generation when using opkg
Date: Tue, 3 May 2016 10:26:10 -0500	[thread overview]
Message-ID: <5728C312.9020902@ni.com> (raw)
In-Reply-To: <1462261759.23261.18.camel@intel.com>



On 05/03/2016 02:49 AM, Patrick Ohly wrote:
> But how does opkg know that "config file not present" is an error? It
> depends on the the semantic of the file and thus the package providing
> the file. It's not declared explicitly, so it is a fairly arbitrary
> judgment call to treat "missing" as error.

I agree. What I meant when I said that "opkg status" output is pretty rough is
that it is making blanket assumptions, and dumping unprocessed metadata. Dpkg -V
analyses the md5sum of each file to determine if it changed, and reports changed
files. While opkg currently only stores the md5sum of conffiles, I think opkg
status should behave similarly to dpkg -V (for conffiles, at least).

Do you mind filing a bug ticket on bugzilla for opkg?

-- 
Cheers,

Alejandro


      reply	other threads:[~2016-05-03 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 13:51 [PATCH] lib/oe/rootfs: Fix DEBUGFS generation when using opkg Richard Purdie
2016-05-02  8:20 ` Anders Darander
2016-05-02 13:39 ` Patrick Ohly
2016-05-02 16:15   ` Alejandro del Castillo
2016-05-03  7:49     ` Patrick Ohly
2016-05-03 15:26       ` Alejandro del Castillo [this message]

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=5728C312.9020902@ni.com \
    --to=alejandro.delcastillo@ni.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patrick.ohly@intel.com \
    /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.