[Dev] [RFC] Voting about package naming for packages modified from Arch

André Silva emulatorman at riseup.net
Fri Aug 29 20:42:11 GMT 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/29/2014 03:20 PM, Micha? Mas?owski wrote:
>> 5) a. Patch makepkg to make pkgrel more flexible (it is already
>> more flexible in pacman/alpm). d. When repackaging a package
>> (without modifying the packaged software), set its
>> pkgrel="${archrel}.parabola${parabolarel}" (which is enabled by
>> the makepkg patch mentioned above).
> 
> Ok, can be done independently of the renaming.
> 
>> b. When forking a package for freedom reasons, name the fork
>> with the '-libre' suffix (example: Linux-libre is a fork of
>> Linux (though it is not maintained by us)). c. When forking a
>> package for technical reasons, name the fork with the '-parabola'
>> suffix (example: patching makepkg as mentioned above would be
>> pacman-parabola).
> 
> Not ok, as explained earlier.  Doing (d) informs users that we
> change the package without adding any compatibility or upgrade
> issues of renaming and is simpler.  Debian-based distros change
> their equivalent of pkgrel.
> 
> Or is there any case of "forking" that results in incompatible
> packages that should not have replaces= or provides= arrays listing
> the original package?
> 
>> e. Whe packaging a kernel module package (or other package 
>> specific to a kernel version), name it 
>> "${_pkgbase}${_kernelname}" and give it 
>> pkgrel=${archrel}.parabola${parabolarel}.${_basekernel}" f. The
>> kernelname/version stuff we already just switched to.
> 
> Ok.
> 
> 

+1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJUAOWjAAoJEOaXR1L5cERWdO4P/2ylIG8iu+bg8gg0iys7XqMD
U4nXwJerUXDHvWNcZziQ0Jydm3yWpIJ4jBP5Tb/p9+bLiphFyTP2R9Y/OYFPhHlr
Ia2PtoBEaE7xP1O+sCBVjrpaTxv9dRsac5F+gpq72QxF6NcMSLH+cKhYI21eqBiA
i5PDNIrnUTKBvtoUiXITKUIbeH7DnEU0jX6mNq8DJtP71j3gqgfm3h9WoEfNx/BG
zYSXz7SeFHehO0p/gFZT1ASlm6sCBgNKUYxP1CFPri6Z7biu3wd8xiLmuisXF9v7
bODQ8W/qOY092rEfLA4NQhNMA4bG68lQ0ScLtrFn5S2B82QMYrG//QUArCVdH1nH
QR9SEKn6WRONF43hcczcPjts5lo6fCK/iYYyqZBCLdCEplaV6CdgNpJUdTPabCl3
5qC+VC2Wrce8bCfie95Toct/vRkvPSPuWHqJ6jnVmydvTSdxdNJgay6N1Npm5L3Q
3zxruhg8P88wKIqqcIm1x4kM3QkbCWAAQtyfROcA0UF4BSIMSelGZJfbeMcNGkEs
f9BuOWAPZp4mkvugfKFSYJoMkpULpDqOQJDiAksUoIDOQ8ZnylUGdDUoj8dUCHHm
HjCSGxLzsU3K78eoRJAdYgF9KON63r0L9ZeBKnh2zQh87YChLXX+Ztot/TDnOmyW
EtdkXufZmZGAmsLm6Saz
=6tXF
-----END PGP SIGNATURE-----



More information about the Dev mailing list