From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Cc: Robert Schuster <theBohemian@gmx.net>
Subject: Re: custom debian package names and fully customized package names
Date: Sun, 06 Jan 2008 17:14:44 +0000 [thread overview]
Message-ID: <1199639684.4658.22.camel@localhost.localdomain> (raw)
In-Reply-To: <751916312.20080103125213@gmail.com>
On Thu, 2008-01-03 at 12:52 +0200, Paul Sokolovsky wrote:
> Wednesday, January 2, 2008, 3:04:12 PM, you wrote:
> > I have found a simple solution for allowing one to customize the Debian
> > package names:
>
> > http://bugs.openembedded.org/show_bug.cgi?id=3383
>
> > Please have a look at it and tell me whether you want it like this.
>
> > This patch is primarily meant to make custom python code to fix wrong
> > guessing of the Debian renamer unnecessary.
Something like the above is ok with me.
> > I have another patch that allows fully customized package names. This
> > efforts may be useless from a distro building POV but is IMHO vital for
> > all those who want to use OE to build packages for a non-OE distro.
>
> > http://bugs.openembedded.org/show_bug.cgi?id=3590
>
> > Comments on both enhancements are welcomed!
>
> Ideas look good for me. Wouldn't solution from #3590 supercede one
> from #3383? (If the tasks were given appropriate order.)
I don't think this is needed, you can do this with overrides already.
I've commented on the bug accordingly.
Cheers,
Richard
prev parent reply other threads:[~2008-01-06 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 13:04 custom debian package names and fully customized package names Robert Schuster
2008-01-03 10:52 ` Paul Sokolovsky
2008-01-06 17:14 ` Richard Purdie [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=1199639684.4658.22.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
--cc=theBohemian@gmx.net \
/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.