All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: SELinux <selinux@tycho.nsa.gov>,
	Selinux on Fedora discussion <selinux@lists.fedoraproject.org>
Subject: Fedora COPR repositories with builds of latest code
Date: Wed, 24 May 2017 16:22:08 +0200	[thread overview]
Message-ID: <b95f2f22-9280-2448-9fd2-cede379bff8d@redhat.com> (raw)

For the motivation see
https://marc.info/?l=selinux&m=149435307518336&w=2

I've restarted building of Fedora packages based on latest SELinux 
userspace code in Fedora COPR. Packages are built using the 
https://gitlab.com/bachradsusi/selinux-rpm project.

There is a new selinux.spec [1] file which allows to build all Fedora 
packages from one src.rpm and Makefile which makes the process simple.

Currently there are two COPR projects:

* https://copr.fedorainfracloud.org/coprs/plautrba/selinux-fedora/

This is built with Python3 support based on Fedora patches which are 
rebased against latest upstream code.


* https://copr.fedorainfracloud.org/coprs/plautrba/selinux-SELinuxProject/

This is based on pure upstream sources and without Python 3.


Currently I run copr builds manually but the plan is to make it fully 
automated.


Let me know if you find it useful or if you have ideas, comments and so on.


[1] https://gitlab.com/bachradsusi/selinux-rpm/blob/master/selinux.spec


Thanks,

Petr

             reply	other threads:[~2017-05-24 14:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 14:22 Petr Lautrbach [this message]
2017-05-24 14:33 ` Fedora COPR repositories with builds of latest code Dominick Grift
2017-05-24 14:53   ` Dominick Grift
2017-05-24 20:40     ` Stephen Smalley
2017-05-25  5:44       ` Dominick Grift
2017-05-25  9:40         ` Petr Lautrbach
2017-05-25 10:07           ` Dominick Grift
2017-05-24 14:43 ` Paul Moore

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=b95f2f22-9280-2448-9fd2-cede379bff8d@redhat.com \
    --to=plautrba@redhat.com \
    --cc=selinux@lists.fedoraproject.org \
    --cc=selinux@tycho.nsa.gov \
    /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.