From: Tom Rini <trini@embeddedalley.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: interest in binary packaging?
Date: Thu, 24 Sep 2009 12:52:03 -0700 [thread overview]
Message-ID: <20090924195203.GH9726@smtp.west.cox.net> (raw)
In-Reply-To: <1253226007.1495.264.camel@conroy-linux>
On Thu, Sep 17, 2009 at 06:20:07PM -0400, Chris Conroy wrote:
> I've developed a rather simplistic method for managing "binary" packages
> within OE in order to satisfy certain licensing requirements. I am not
> sure whether other users would have an interest in such a system, but
> I'll go ahead and pitch what I have working so far to see if there is
> any interest in improving it further or merging upstream.
Yes, there is interest. The only issue I see off the top of my head is
that this doesn't work for deb / rpm / tar, when it could. The way I've
solved this before is to have the binary version just be a tarball of
the do_install() from the source version, Then -dbg/-dev/whatever gets
split up normally and other output formats work fine too.
--
Tom Rini
prev parent reply other threads:[~2009-09-24 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 22:20 interest in binary packaging? Chris Conroy
2009-09-24 19:52 ` Tom Rini [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=20090924195203.GH9726@smtp.west.cox.net \
--to=trini@embeddedalley.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.