| Age | Commit message (Collapse) | Author |
|---|
|
As the PKGBUILD was only tested with makepkg, and that git
was already installed, it didn't pick the issue at build
time.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
In archlinux, archlinux32, archlinuxarm, Parabola,
and probably other archlinux derivative, the PKGBUILD
lack a license.
I was told on #archlinux that the PKGBUILDS were
copyrightable but at the same time that nobody cared enough
about licensing to fix this issue.
According to what I was told in this channel, that the
only thing to do to move things forward would be to start
adding a license to PKGBUILDs to force archlinux to fix its
licensing.
As I've created this PKGBUILD from scratch, I've now added
a GPLv3 license.
I'm also open to relicense it under other free software
licenses as well, in order to get this copyright issue
fixed.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
This adds fso-unbootimg.
In archlinux, archlinux32, archlinuxarm, Parabola,
and probably other archlinux derivative, the PKGBUILD
lack a license.
I was told on #archlinux that the PKGBUILDS were
copyrightable but at the same time that nobody cared enough
about licensing to fix this issue.
According to what I was told in this channel, that the
only thing to do to move things forward would be to start
adding a license to PKGBUILDs to force archlinux to fix its
licensing.
As I've created this PKGBUILD from scratch, I've included a
GPLv3 license as well.
I'm also open to relicense it under other free software
licenses as well, in order to get this copyright issue
fixed.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
it's on [nonsystemd] now
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
|
|
|
|
|
|
While meson is used upstream, autools were kept for now,
as converting to meson requires more changes.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
java environment (aka for jdk/jre8 for them)
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Related to #2405
|
|
#2405
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
I forgot to git-add the changes. This should fix the
package rename.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Linux-libre and winetricks-libre are project names.
Other packages usually keep the same name than the original
ones.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
This doesn't contain any tests yet. Some could be added back by
not deleting them from ob-cache/.
Tests like build-gcc should be OK to bring back as they
only consists in downloading the GCC source code, checking
its checksum, and compiling it. Since GCC is fully free
software and that they use the official releases, it should
be safe to bring them back.
Some other tests are more problematic:
- Some tests like build-linux use source code is not fully
free. This should be removed. Using linux-libre instead
would be possible, but a different test would need to be
written for that.
- Some like xonotic uses official binaries, which is a
problem since we might want not to trust binaries, and we
also don't know how they were built, so we cannot ensure
that they are buildable on FSDG distributions. Again such
tests would need to be removed or forked not to create
problematic test results.
- Some like build-imagemagick download source code from the
phoronix-test-suite website. To use that we would need to
ensure that the released source code is the same than the
one released by the upstream project. If not we could
either remove theses tests or patch the official source
to reproduce an equivalent tarball in a way that can be
more easily reviewed.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The instructions to flash are based on information from uboot's
doc/imx/mkimage/imximage.txt document.
As for the USB Armory which uses an I.MX 53, the it also uses the
same offset as documented in an u-boot installation guide:
https://github.com/inversepath/usbarmory/wiki/Secure-boot-(Mk-I)#user-content-prepare-and-flash-the-signed-u-boot
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
This was build tested on i686.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
This was build tested on i686.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The AUR PKGBUILD of kiwix-tools now need this version of
mustache.
This was build tested on 686.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
This was build tested on 686.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
libre/linux-libre-chromebook is confirmed to work, otherwise I'll build an special CrOS kernel in [libre]
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
