aboutsummaryrefslogtreecommitdiff
path: root/configs/beagleboardx15_defconfig
diff options
context:
space:
mode:
authorGravatar Victor Huesca <victor.huesca@bootlin.com>2019-06-12 08:42:08 +0200
committerGravatar Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>2019-06-19 23:26:35 +0200
commitb34ead55c06cad5b6443da358cd63e9c71265d69 (patch)
treec606668708c0796fcd7051521cd4cfd4027c8e49 /configs/beagleboardx15_defconfig
parent69808c7536de5a67dc8bc363f4b56e0097d6a9d1 (diff)
downloadbuildroot-master.tar.gz
buildroot-master.tar.bz2
package: remove non-conventional prefix/suffix from github-fetched packagesHEADmaster
On Github, a large number of projects name their tag <some-prefix>-0.3-<some-suffix> (i.e release-3.0, poco-0.1-release, etc.). In fact majority of the cased adressed in this commit concerns prefixes. In most packages, we encode those prefix/suffix in the <pkg>_VERSION variable. The problem with this approach is that when used in conjunction with release-monitoring.org, it doesn't work very well, because release-monitoring.org has the concept of "version prefix/suffix" and using that they drop the prefix/suffix to really get the version. For example on https://release-monitoring.org/project/5418/ the latest release of "poco" is "1.8.1", not "poco-1.8.1-release". Therefore, a number of packages in Buildroot have a version that doesn't match with release-monitoring.org. Since really the version number of 1.8.1, is makes sense to update our packages to drop these prefixes/suffixes. This commit addreses the case of github-fetched packages with non-conventional prefixes/suffixes. Note that these changes modify the name of the files stored in DL_DIR, which means that this will force a re-download of those package source code for all users, and requires a change to their .hash file. Signed-off-by: Victor Huesca <victor.huesca@bootlin.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Diffstat (limited to 'configs/beagleboardx15_defconfig')
0 files changed, 0 insertions, 0 deletions