Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
and i686
|
|
|
|
The changes to the PKGBUILDs should actually happen on a per-package level in our modification repository
|
|
|
|
archive (currently only "git")
|
|
repositories by tarballs
|
|
PKGBUILD - retrieve kernel git repository snapshot from our archive server instead of cloning the git repository
|
|
|
|
|
|
toolchain_order correctly
|
|
|
|
|
|
|
|
not yet in FOREIGN KEYs
|
|
|
|
|
|
|
|
blacklist_packages
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
all replaced_bpir :-/
|
|
|
|
repository.
|
|
|
|
all built packages will be compatible in the indicated way (in contrast to: instruction set of arch $x is a subset of arch $y) - beware of linking against libraries compiled for different architectures!
|
|
|
|
|
|
|
|
|
|
instead of stability name
|
|
|
|
|
|
|
|
|
|
columns in `binary_packages_in_repositories`, not `binary_packages`
|
|
|
|
|
|
|