All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Koen Kooi <openembedded-devel@lists.openembedded.org>
Subject: Re: Fixing ipkg-make-index slowness
Date: Fri, 5 Jan 2007 11:33:13 +0200	[thread overview]
Message-ID: <1725097716.20070105113313@gmail.com> (raw)
In-Reply-To: <459E18AF.5040308@dominion.kabel.utwente.nl>

Hello Koen,

Friday, January 5, 2007, 11:21:51 AM, you wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Paul Sokolovsky schreef:

>> 
>> Richard, what were the reasons for such conservative file matching?
>> Filename matching should be just enough, as per OE convention, any
>> package source changes leading to changes in the package metadata must
>> lead to bumping of package recipe's PR, and that in turn updates package
>> filename.

> It isn't enough. If you repackages the exact same files at a later date, the timestamps in
> the tarball have changed, and hence the md5 will be different. When a user will download a
> package ipkg will check the md5sum present in the index and abort if it doesn't match.

  Then we probably need to separate image building from feed
creation/setup. IIRC, i-m-i currently run during image building
too, and it steals precious minutes from each developer (vs
distro/feed maintainer) multiple times a day. Having Packages
to be updated only by explicit "bitbake package-index" seems
like good compromise and corresponds to the docs which suggest
to do that explicitly.

> regards,

> Koen

-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  reply	other threads:[~2007-01-05  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05  7:33 Fixing ipkg-make-index slowness Paul Sokolovsky
2007-01-05  9:21 ` Koen Kooi
2007-01-05  9:33   ` Paul Sokolovsky [this message]
2007-01-05  9:59     ` Koen Kooi
2007-01-05 11:52 ` Richard Purdie

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=1725097716.20070105113313@gmail.com \
    --to=pmiscml@gmail.com \
    --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.