From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC PATCH 1/3] imx-uuc: new package
Date: Thu, 26 Mar 2020 10:59:49 +0100 [thread overview]
Message-ID: <CABDcavbT-FxOaGZycBAtWUe8FMDO+GBRwMiSvp4D7CVnubyF1g@mail.gmail.com> (raw)
In-Reply-To: <20200325184346.jbb3dt3nnj46bwbm@pengutronix.de>
El mié., 25 mar. 2020 a las 19:44, Roland Hieber
(<rhi@pengutronix.de>) escribió:
> > +IMX_UUC_VERSION := d6afb27e55d73d7ad08cd2dd51c784d8ec9694dc
>
> Nitpick: I don't know how picky opkg-based systems are with having
> monotonically increasing version numbers, but in case someone uses them
> to update software, you could make them happy by providing a fake
> 'git describe' tag as a version:
It is picky, and will refuse to upgrade if the version number seems to
be lower than whatever is currently installed.
So yes, the package version should be monotonically increasing and not
simply a commit hash.
When I face this case in my own packages I normally define two
different varaibles, e.g.:
IMX_UUC_VERSION := 0.0.1
IMX_UUC_GIT_TAG := d6afb27e55d73d7ad08cd2dd51c784d8ec9694dc
and then use IMX_UUC_VERSION everywhere except in the URL:
IMX_UUC_URL :=
https://github.com/NXPmicro/imx-uuc.git;tag=$(IMX_UUC_GIT_TAG)
Guillermo
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2020-03-26 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 14:53 [ptxdist] [RFC PATCH 0/3] Freescale/NXP i.MX mfgtools 3.0 Denis Osterland-Heim
2020-03-24 14:53 ` [ptxdist] [RFC PATCH 2/3] host-libzip: new package Denis Osterland-Heim
2020-03-24 14:53 ` [ptxdist] [RFC PATCH 3/3] host-mfgtools: " Denis Osterland-Heim
2020-03-25 18:33 ` Roland Hieber
2020-03-26 8:28 ` Denis Osterland-Heim
2020-03-26 16:16 ` Michael Olbrich
2020-03-26 16:25 ` Denis Osterland-Heim
2020-03-24 14:53 ` [ptxdist] [RFC PATCH 1/3] imx-uuc: " Denis Osterland-Heim
2020-03-25 18:43 ` Roland Hieber
2020-03-25 18:52 ` Roland Hieber
2020-03-25 20:40 ` Roland Hieber
2020-03-26 9:03 ` Denis Osterland-Heim
2020-03-26 9:47 ` rhi
2020-03-26 16:23 ` Michael Olbrich
2020-03-26 16:32 ` Denis Osterland-Heim
2020-03-26 9:59 ` Guillermo Rodriguez Garcia [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=CABDcavbT-FxOaGZycBAtWUe8FMDO+GBRwMiSvp4D7CVnubyF1g@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.de \
/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