| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
updatelanglist.sh to manage shasums
|
|
|
|
this package can be removed once the arch package is working again
https://bugs.archlinux.org/task/65898
|
|
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
|
|
|
|
|
|
originally, the libre.patch simply deleted the documentation usage examples;
because they referred to non-FSDG-fit distros;
and the 'osinfo-db' package has no definitions for FSDG-fit distros
this commit adds back the usage examples, referring to FSDG distros instead
the exact usage examples given will not work, without also adding
the 'parabola' definition to the osinfo database
the documentation is complete however; so that is already an improvement
we could fork the 'osinfo-db' package, to add the parabola definition;
but experimentation suggests that it can be accomplished
via the 'libosinfo' package, which parabola already patches
ideally, we should request that parabola be added to the osinfo-db upstream
(which is probably a good idea anyways)
|
|
the changes in this patch are more extensive
than what the commit message would suggest
they are predominantly for the sake of
minimizing the diff with upstream
this is a split package upstream; but only 'virt-install' is on the blacklist
originally, the package_virt-manager() function was deleted
and the package_virt-install() function was left in tact,
including the code that splits the output files into two packages
that made this PKGBUILD quite confusing:
* the pkgbase and abslibre directory are named 'virt-manager'
* the PKGBUILD is still formatted as a split package,
which happens to output only one single package
* some non-package files are stashed aside, for apparently no reason,
rather than making the intention obvious by deleting them
all of the work necessary to output the 'virt-manager' package,
is necessarily done by this PKGBUILD while building 'virt-install'
(the package_virt-manager() function is merely a `mv` statement);
so there is no reason not to package both
packaging 'virt-manager' also has the benefit, of the pinned
'virt-install' dependency of 'virt-manager', being always satisfiable
been added to the blacklist with reason: 'technical'
virt-manager has been added to the blacklist with reason: 'technical'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Without that fix, on i686 we have:
$ drm_info
drm_info: error while loading shared libraries: libjson-c.so.4:
cannot open shared object file: No such file or directory
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
|
|
|
|
|
|
|
|
This seems to be related only to crashreporter that is disabled anyway.
|
|
Setting MOZ_APP_NAME is necessary now because paths to binaries will
contain 'firefox' not 'iceweasel' due to changes in this release of
upstream Firefox.
|
|
Also removed leftover flags dropped by upstream in 80.0-1, See:
https://github.com/archlinux/svntogit-packages/commit/7f7808aed43c21887a9b440005b6aca4e9295b9d#diff-91e904bd64036c9c236ce84542f97781L112
These flags probably should be removed for i686 too, but I was
not able to build it with or without them anyway.
|
|
These let DuckDuckGo know the place in UI the search ran from. For
example, the resulting search URL from address bar:
https://html.duckduckgo.com/html/?t=ffab&q=parabola
where t=ffab is the parameter in question. See unpatched file in
the source tree for possible values of this parameter:
browser/components/search/extensions/ddg/manifest.json
|
|
|
|
|
|
|
|
|
|
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>
|
|
|
|
|
|
|
|
although the version number has not changed,
this version is built from different sources than the previous "version"
the highest version number in the ChangeLog is 1.2.1
the version number of this package was taken from the 'VERSION' in the sources
however, the upstream did not change either version numbers
and neither did the packager; so the pkgver is meaningless
this software is a fork - the original software had versioned releases;
but AFAICT, this fork has no versioned releases
the version number itself, indicates that it is volatile pre-release software,
with little assurance of the permanence of the VCS commit from which this is built
all of this together, suggests that this should be a -git package,
to give users fair warning that it is volatile and unlikely to be supported upstream
|
|
|
|
Building Guix from within Parabola is better as:
- It rebuilds guix from source, so we don't rely on more binaries.
In addition it enables to test reproducible builds when built from
Parabola.
- We end up with less space being taken by dependencies at the beginning
as the dependencies are shared with other Parabola packages.
However building Guix didn't work well on i686 for instance, and it's also
a good idea to provide guix's installer as well as there are different
tradeoffs being made between the installer packages built within Parabola.
For instance Guix binaries are built against Guile3 which isn't in Parabola
yet.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
only the changes to profile and shadow are significant
the rest are trivial housekeeping,
to minimize the diffs across the arch and libre PKGBUILDs
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
