All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ipkg/opkg offical response
Date: Fri, 28 Mar 2008 10:45:15 +1030	[thread overview]
Message-ID: <47EC3893.80908@whitby.id.au> (raw)
In-Reply-To: <200803272104.30232.openembedded@haerwu.biz>

Marcin Juszkiewicz wrote:
> So creation of "opkg-nogpg":
> 
> require opkg_svn.bb
> EXTRA_OECONF += "--disable-gpg"
> 
> would be nice addon. Creation of "curl-nossl" and selecting it is 
> something which should be rather DISTRO choice as it generate same 
> packages as "curl" recipe.

+1

> Solution would be creating DISTRO_IPK_PACKAGE_MANAGER ?= "opkg" and using 
> it in package_ipk/rootfs_ipk and other places. Then staging 
> ipkg-cl/opkg-cl as ipkg/opkg so we can use "${DISTRO_IPK_PACKAGE_MANAGER} 
> update". Distros which prefer to use ipkg will stay with it, others will 
> move to opkg.

Can we simplify to DISTRO_PACKAGE_MANAGER?  Will we ever want ipks and 
debs to be produced at the same time?

-- Rod



  reply	other threads:[~2008-03-28  0:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 17:17 ipkg/opkg offical response Richard Purdie
2008-03-27 19:25 ` Koen Kooi
2008-03-27 22:57   ` Jeremy Lainé
2008-03-27 23:09     ` Tom Rini
2008-03-28  0:30       ` Leon Woestenberg
2008-03-28  9:20         ` Richard Purdie
2008-03-28  9:43           ` Koen Kooi
2008-03-28  4:23       ` Marcin Juszkiewicz
2008-03-27 23:07   ` Richard Purdie
2008-03-28  7:03     ` kernel breackage, was " Koen Kooi
2008-03-28  9:17       ` Richard Purdie
2008-03-28  9:35         ` Koen Kooi
2008-03-27 20:04 ` Marcin Juszkiewicz
2008-03-28  0:15   ` Rod Whitby [this message]
2008-03-28  6:56     ` Koen Kooi
2008-03-28  9:27     ` Richard Purdie
2008-08-21  6:48       ` Mike (mwester)
2008-03-28 16:17   ` Jeremy Lainé

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=47EC3893.80908@whitby.id.au \
    --to=rod@whitby.id.au \
    --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.