From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] tinylogin: use angstrom mirror for SRC_URI
Date: Thu, 07 Jul 2011 11:29:09 +0100 [thread overview]
Message-ID: <1310034549.20015.816.camel@rex> (raw)
In-Reply-To: <1308148061.25285.1764.camel@phil-desktop>
On Wed, 2011-06-15 at 15:27 +0100, Phil Blundell wrote:
> since busybox.net no longer seems to be hosting the tarball
>
> Signed-off-by: Phil Blundell <philb@gnu.org>
> ---
> meta/recipes-core/tinylogin/tinylogin_1.4.bb | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-core/tinylogin/tinylogin_1.4.bb b/meta/recipes-core/tinylogin/tinylogin_1.4.bb
> index 0b51b25..b73b5b7 100644
> --- a/meta/recipes-core/tinylogin/tinylogin_1.4.bb
> +++ b/meta/recipes-core/tinylogin/tinylogin_1.4.bb
> @@ -9,7 +9,7 @@ LICENSE = "GPLv2"
> LIC_FILES_CHKSUM="file://LICENSE;md5=f1060fa3a366f098b5b1d8c2077ba269"
> PR = "r6"
>
> -SRC_URI = "http://tinylogin.busybox.net/downloads/tinylogin-${PV}.tar.bz2 \
> +SRC_URI = "http://www.angstrom-distribution.org/unstable/sources/tinylogin-${PV}.tar.bz2 \
> file://cvs-20040608.patch;patch=1;pnum=1 \
> file://add-system.patch;patch=1;pnum=1 \
> file://adduser-empty_pwd.patch;patch=1 \
Merged to master, thanks.
Longer term, I wonder if we could make this recipe download and build
busybox but only build the getty/login parts and rename the resulting
static binary to be standalone from busybox itself?
That would likely address the concerns people (rightly IMO) have about
making busybox itself SUID...
Cheers,
Richard
next prev parent reply other threads:[~2011-07-07 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 14:27 [PATCH] tinylogin: use angstrom mirror for SRC_URI Phil Blundell
2011-07-07 10:29 ` Richard Purdie [this message]
2011-07-07 10:45 ` Phil Blundell
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=1310034549.20015.816.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox