From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] ptxd_lib_dgen.awk: $(STATEDIR)/*.targetinstall.post depends on $(PKGDIR)/Packages
Date: Thu, 27 Oct 2011 13:21:28 -0400 [thread overview]
Message-ID: <CAMwGMjyenmF_kEOz_2vY7=m55HuTeZQBw5b41kAM8g-cuAJUNg@mail.gmail.com> (raw)
In-Reply-To: <20111027170519.GJ30634@pengutronix.de>
On Thu, Oct 27, 2011 at 1:05 PM, Michael Olbrich
<m.olbrich@pengutronix.de> wrote:
> On Thu, Oct 27, 2011 at 12:02:21PM -0400, Jon Ringle wrote:
>> On Thu, Oct 27, 2011 at 11:12 AM, Michael Olbrich
>> <m.olbrich@pengutronix.de> wrote:
>> > Please elaborate why this is necessary.
>>
>> Doing this makes it possible for a developer to point opkg.conf on the
>> target to a URL that resolves to platform/packages/. A developer that
>> is working on a single package can then just do ptxdist targetinstall
>> foo and on the target:
>> opkg update
>> opkg remove foo
>> opkg install foo
>>
>> Doing ptxdist images and having the ipkg-repository updated takes too
>> long when all one is interested is the update of a single .ipkg file
>
> I see what you mean. However I'm pretty sure, that with this patch if you
> run "ptxdist images" in a clean BSP you'll get a broken Packages file
> because it's created too early.
> It running "ptxdist targetinstall foo && ptxdist make ipkg-index" not good
> enough?
I'm sure that "ptxdist make ipkg-index" will work. I just didn't know
how to invoke that rule before now :)
Jon
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2011-10-27 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 13:42 Jon Ringle
2011-10-27 15:12 ` Michael Olbrich
2011-10-27 16:02 ` Jon Ringle
2011-10-27 17:05 ` Michael Olbrich
2011-10-27 17:21 ` Jon Ringle [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='CAMwGMjyenmF_kEOz_2vY7=m55HuTeZQBw5b41kAM8g-cuAJUNg@mail.gmail.com' \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/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