Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] package/swupdate: new package
Date: Mon, 27 Apr 2015 21:02:56 +0200	[thread overview]
Message-ID: <1430161376.1537.5.camel@embedded.rocks> (raw)
In-Reply-To: <20150425102232.GB4275@free.fr>

Hi Yann,

On Sa, 2015-04-25 at 12:22 +0200, Yann E. MORIN wrote:
> J?rg, All,
> 

[snip]

> 
> We prefer to point to the homepage when it exists, rather than to the
> git tree:
>     https://sbabic.github.io/swupdate/

Ok.

> 
> > +if BR2_PACKAGE_SWUPDATE
> > +
> > +config BR2_PACKAGE_SWUPDATE_CONFIG
> > +   string "swupdate configuration file"
> > +   default "package/swupdate/swupdate.config"
> > +   help
> > +     The default swupdate configuration file will enable 
> > swupdate with
> > +     an image downloader and a webserver, as well as 
> > handlers for UBI
> > +     volumes, raw NAND or NOR flash, SD cards and shell 
> > scripts.
> > +
> > +     Most people will just use the default swupdate 
> > configuration file.
> > +     However, some people may wish to use their own modified 
> > swupdate
> > +     configuration file, and will specify their config file 
> > location
> > +     with this option.
> > +
> > +     Note that if you add lua support in the configuration 
> > file you need
> > +     the Lua 5.2 interpreter (BR_PACKAGE_LUA_5_2) manually.
> 
> Something's weird in this sentence. What about:
> 
>     Note that if you add lua support in the configuration file, you 
> will
>     have to enable the Lua 5.2 interpreter (BR_PACKAGE_LUA_5_2).

Ok.

> 
> [--SNIP--]
> > diff --git a/package/swupdate/swupdate.mk 
> > b/package/swupdate/swupdate.mk
> > new file mode 100644
> > index 0000000..71ae888
> > --- /dev/null
> > +++ b/package/swupdate/swupdate.mk
> > @@ -0,0 +1,53 @@
> > +##################################################################
> > ##############
> > +#
> > +# swupdate
> > +#
> > +##################################################################
> > ##############
> > +
> > +SWUPDATE_VERSION = c68f02320858f89f2d441ff2057d49489fb6f586
> > +SWUPDATE_SITE = $(call github,sbabic,swupdate,$(SWUPDATE_VERSION))
> > +SWUPDATE_LICENSE = GPLv2+
> 
> In fact, there are a few other licenses. For example, the copies of
> Mongoose and lsqlite3 they bundle are MIT; the sqlite3 aggregated 
> source
> file is public domain ("The author disclaims copyright to this source
> code.").

I see. So I'll add MIT and Public Domain, right?

> > +SWUPDATE_LICENSE_FILES = COPYING
> > +
> > +# swupdate bundles its own mongoose and lsqlite3 versions
> 
> Is it possible to make it use external versions, or does it only 
> support
> using its bundled ones?
> 
> If that's possible, we prefer that.

swupdate bundles with mongoose 3.8 (2013) and lsqlite3 0.8 (2011)
versions. I'm not sure it will work with recent versions.

Best regards
J?rg Krause

      parent reply	other threads:[~2015-04-27 19:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-24 23:02 [Buildroot] [PATCH v4 1/1] package/swupdate: new package Jörg Krause
2015-04-25 10:22 ` Yann E. MORIN
2015-04-25 12:30   ` Thomas Petazzoni
2015-04-25 13:53   ` Romain Naour
2015-04-27 19:02   ` Jörg Krause [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=1430161376.1537.5.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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