From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/8] Bump of SElinux related libs/tools to 3.0
Date: Tue, 14 Apr 2020 18:23:03 +0200 [thread overview]
Message-ID: <20200414182303.250cc38d@windsurf.home> (raw)
In-Reply-To: <20200414152528.20758-1-matthew.weber@rockwellcollins.com>
On Tue, 14 Apr 2020 10:25:20 -0500
Matt Weber <matthew.weber@rockwellcollins.com> wrote:
> - Switches to using the date (i.e. 20191204) abased release tagging
> for better alignment with https://release-monitoring.org/project/01717/
>
> - Added selinux-python which was missed in the v2 of this bump by
> Adam (http://patchwork.ozlabs.org/project/buildroot/list/?series=156673)
I am not sure I like the change to using the single big tarball with
everything included, and then have each individual package build its
own sub-directory. They ship individual tarballs, it seems a lot better
to use that.
Is the only benefit of that change the fact that it will match with
what release monitoring says ?
Even Fedora, who is the original project using release-monitoring uses
the real version numbers for SELinux:
$ rpm -qa | grep libselinux
libselinux-utils-2.9-5.fc31.x86_64
libselinux-2.9-5.fc31.i686
libselinux-devel-2.9-5.fc31.x86_64
libselinux-2.9-5.fc31.x86_64
So to me, it seems like we should instead change the versions reported
by release-monitoring.org instead.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-14 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 15:25 [Buildroot] [PATCH v3 0/8] Bump of SElinux related libs/tools to 3.0 Matt Weber
2020-04-14 15:25 ` [Buildroot] [PATCH v3 1/8] package/libselinux: bump version " Matt Weber
2020-04-14 15:25 ` [Buildroot] [PATCH v3 2/8] package/libsemanage: " Matt Weber
2020-04-14 15:25 ` [Buildroot] [PATCH v3 3/8] package/libsepol: " Matt Weber
2020-04-14 15:25 ` [Buildroot] [PATCH v3 4/8] package/policycoreutils: " Matt Weber
2020-04-14 15:25 ` [Buildroot] [PATCH v3 5/8] package/restorecond: " Matt Weber
2020-04-14 15:25 ` [Buildroot] [PATCH v3 6/8] package/semodule-utils: " Matt Weber
2020-04-14 15:25 ` [Buildroot] [PATCH v3 7/8] package/checkpolicy: " Matt Weber
2020-04-14 15:25 ` [Buildroot] [PATCH v3 8/8] package/selinux-python: bump to version 3.0 Matt Weber
2020-04-14 16:23 ` Thomas Petazzoni [this message]
2020-04-14 17:20 ` [Buildroot] [PATCH v3 0/8] Bump of SElinux related libs/tools to 3.0 Matthew Weber
2020-04-15 5:43 ` Thomas Petazzoni
2020-04-15 7:40 ` Arnout Vandecappelle
2020-04-15 19:52 ` Yann E. MORIN
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=20200414182303.250cc38d@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.