In my case, whenever I build a package which does not correspond to [libre], I put it in [pcr]. Now, you may ask, what goes in [libre]? In my case, besides the obvious stuff (libre replacements) I also upload dependencies of [libre] packages (e.g. linux-libre-firmware cross-compilers), and you can also see Parabola's developers tools and related stuff.
I've also faced that issue, build Arch packages for ARM which aren't in ALARM, and in that case I put them in [pcr], because they're not a [libre] replacement and aren't needed by any [libre] pkgs, at least for ARM. El 15-04-20 a las 22:17, Denis 'GNUtoo' Carikli escribió: > Hi, > > I want to build a Xonotic package for Parabola ARM, that I then upload > using librerelease, in order to make it available to everyone. > > So I was suggested by Bill Auger to either convince archlinuxarm to > built it for me, or to add the Xonotic PKGBUILD in pcr. > > As before the discussion I thought that the PCR repository was meant > for PKGBUILDs that would be imported from AUR and potentially modified, > and not for packages that don't fit in all other repositories, it > triggered a discussion on which packages should go where. > > I was asked to start a thread about that on the mailing list. > > According to Bill Auger, there is also different understanding of what > should go in libre. > > Denis. > > > _______________________________________________ > Dev mailing list > Dev@lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Dev mailing list Dev@lists.parabola.nu https://lists.parabola.nu/mailman/listinfo/dev