From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] opkg updates?
Date: Tue, 22 May 2018 18:17:58 +0200 [thread overview]
Message-ID: <20180522181758.411c3adb@windsurf> (raw)
In-Reply-To: <SN6PR02MB3998B8B8B748380B25E9087DF2940@SN6PR02MB3998.namprd02.prod.outlook.com>
Hello Derek,
On Tue, 22 May 2018 15:46:05 +0000, Baker, Derek wrote:
> We've determined that having a more recent version of opkg would make
> our lives easier, but notice that the opkg version that ships with
> buildroot is quite old. Are there plans to update that to a more
> recent version? If not, can someone explain why so I can pass that on
> to my team? If there are plans to update it, can someone let me know
> when that might happen?
Packages are updated when someone sends a patch to update it. So if you
need the opkg package to be updated, we would very much welcome a patch
doing this!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-22 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 15:46 [Buildroot] opkg updates? Baker, Derek
2018-05-22 16:17 ` Thomas Petazzoni [this message]
2018-05-22 16:19 ` Baruch Siach
2018-05-22 19:10 ` Baker, Derek
2018-05-23 2:27 ` Baruch Siach
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=20180522181758.411c3adb@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox