[xiphos-devel] windows build
greg.hellings at gmail.com
Fri Apr 24 10:36:55 MST 2020
I'm looking through xc-xiphos-win.sh and I'm curious:
Can we retool this so that it's just a regular shell script that can be
passed to Docker/podman/etc and it does the installing of deps and builds
internal to itself? Then we can easily invoke it like
(docker|podman) run -i -t -v /path/to/xiphos/source:/xiphos fedora:30
This would make things very much easier for automating builds and allowing
people to test it locally. I don't use toolbox, but I do use Docker
regularly on Fedora 31. And most all of our cloud providers come with
Docker available out of the box, but either don't offer toolbox or it's
going to be a royal pain to get it working on their infra. I'm happy to
undertake this effort, and add it to the CI, if you don't mind.
On Fri, Apr 24, 2020 at 12:26 PM Greg Hellings <greg.hellings at gmail.com>
> Maybe try skipping toolbox and going straight to Podman to test if it can
> do things directly?
> podman run -i -t fedora-toolbox:30 /bin/bash
> On Fri, Apr 24, 2020 at 12:01 PM Karl Kleinpaste <karl at kleinpaste.org>
>> On 4/24/20 11:59 AM, Dominique Corbex wrote:
>> Have you disabled SELinux enabled or running Permissive mode?
>> Oh, is that it?
>> I've run with SELinux disabled since Fedora Core 3, when every update to
>> selinux-policy-targeted threatened to brick my machine. selinux=0 is in my
>> boot flags.
>> I consider it a detailed practical implementation of a theoretical device
>> with little practical value for me, a solution in search of a problem I
>> don't have. But I don't doubt that others will have explanations for its
>> worth. I get better security protection by moving sshd to a nonstandard
>> > If you create a default toolbox:
>> > $ toolbox create
>> > $ toolbox enter
>> > Are you facing the same issue?
>> xiphos-devel mailing list
>> xiphos-devel at crosswire.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the xiphos-devel