From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] dropbear: bump to version 2011.54
Date: Thu, 1 Dec 2011 08:46:00 -0600 [thread overview]
Message-ID: <201112010846.03400.minimod@morethan.org> (raw)
In-Reply-To: <CAAXf6LVMmix+5RSbHDJKj09GGd_60Y6cBtSk2-+qODfOkvm2+g@mail.gmail.com>
On Thu December 1 2011, Thomas De Schampheleire wrote:
> On Thu, Dec 1, 2011 at 2:52 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Le Thu, 1 Dec 2011 07:22:33 -0600,
> > "Michael S. Zick" <minimod@morethan.org> a ?crit :
> >
> >> Has the "DROPBEAR_SOURCE" line been accidentally dropped here?
> >> At "DROPBEAR_SITE" the package is named: dropbear-2011.54.tar.gz
> >> (or .tar.bz2)
> >
> > This <pkg>_SOURCE value is the default one:
> >
> > $(2)_BASE_NAME ?= ?$(1)-$$($(2)_VERSION)
> > $(2)_SOURCE ? ? ?= $$($(2)_BASE_NAME).tar.gz
> >
> > (from package/Makefile.package.in)
>
> Just throwing the question out: should we adapt existing .mk files to
> remove lines that correspond to the default? This is such an example,
> and FOO_INSTALL_TARGET=YES is another one.
>
I would say yes, since people who are adding packages
might pick one of the ones with useless assignments as
their model and then useless assignments would never go
away (or Peter would have to tweak the new patches).
Mike
> Best regards,
> Thomas
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
next prev parent reply other threads:[~2011-12-01 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 8:58 [Buildroot] [git commit] dropbear: bump to version 2011.54 Peter Korsgaard
2011-12-01 13:22 ` Michael S. Zick
2011-12-01 13:52 ` Thomas Petazzoni
2011-12-01 14:00 ` Michael S. Zick
2011-12-01 14:08 ` Thomas Petazzoni
2011-12-01 14:35 ` Thomas De Schampheleire
2011-12-01 14:46 ` Michael S. Zick [this message]
2011-12-01 15:49 ` Peter Korsgaard
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=201112010846.03400.minimod@morethan.org \
--to=minimod@morethan.org \
--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