| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
The PKGBUILD was taken from the Arch Linux community repository
which is at https://github.com/archlinux/svntogit-community as
the old URL (git://git.archlinux.org/svntogit/community.git) isn't
up to date and according to #archlinux, the migration to gitlab
isn't complete yet.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The perf-fix-types.patch has been removed becuase it is already
present in the 5.13.8 kernel upstream with the following commit:
20befbb1080307e70c7893ef9840d32e3ef8ac45 (perf tools: Use %zd
for size_t printf formats on 32-bit).
I updated to 5.13.8 as the linux-libre PKGBUILD aso has that
version.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
As far as I know the android-sdk package is a work in
progress that didn't progress much since 2018. According to the
commit that added it in pcr-testing:
commit d424f0813c7bee07cdea2b6863540e1b84abfb0d
addpkg: pcr-testing/android-sdk-meta
Inspired from https://blog.replicant.us/2017/04/there-wont-be-a-replicant-6-0-sdk-because-there-is-already-something-better/
I used the Debian sources since they are fully-free,
but I still need to add the API level 23 to build an
app, and then move this to [pcr]
In addition, proguard was removed as it was not built from source.
Still it's a good idea to keep that work visible in case someone
wants to add an android-sdk to Parabola.
This way the people wanting to work on that SDK would hopefuly not
redo all the work because they didn't know that someone already
did part of it. So instead they could at least learn from it and
hopefuly save time by reusing what has already been done.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The proguard PKGBUILD doesn't provide any source code for proguard,
and the Aur package it is based on doesn't either.
This is an issue for GPLv2 compliance as well as a practical one:
we cannot patch the software if we need to.
As for the packages that depend on proguard, the android-sdk
package depends on it.
However, as far as I know the android-sdk package is a work in
progress that didn't progress much since 2018. According to the
commit that added it in pcr-testing:
commit d424f0813c7bee07cdea2b6863540e1b84abfb0d
addpkg: pcr-testing/android-sdk-meta
Inspired from https://blog.replicant.us/2017/04/there-wont-be-a-replicant-6-0-sdk-because-there-is-already-something-better/
I used the Debian sources since they are fully-free,
but I still need to add the API level 23 to build an
app, and then move this to [pcr]
So if someone really wants proguard and/or the android-sdk in
Parabola, the solution is to make sure that proguard is built
from source somehow.
In #parabola in liberachat, bill-auger also agreed with me to
the removal of proguard until a way to build it from source
is found.
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>
|
|
otherwise the build fails
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
commits from bcf93cb83 to fbd84207c were WIP experiments
including some that reverted important published changes
none of those should have been published; but they were
and abslibre is ff-only - so this commit undoes the reversions
the other WIP commits in that range are not usable either;
but they do move forward, so they may as well stay
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
