Package Details: localepurge 0.7.3.10-1

Git Clone URL: https://aur.archlinux.org/localepurge.git (read-only, click to copy)
Package Base: localepurge
Description: Script to remove disk space wasted for unneeded localizations.
Upstream URL: http://packages.debian.org/source/sid/localepurge
Keywords: locales
Licenses: GPL
Submitter: None
Maintainer: eddie_vs
Last Packager: eddie_vs
Votes: 263
Popularity: 0.25
First Submitted: 2007-07-08 16:29 (UTC)
Last Updated: 2022-09-24 21:19 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

fgr commented on 2011-05-15 10:01 (UTC)

There are no updates for localepurge script, but I've revised localepurge man page and the PKGBUILD (replaced bash '[[' with sh '[').

fgr commented on 2010-12-18 12:41 (UTC)

I've just moved my patches to another host, renamed the ones from '*.diff' to '*.patch' and changed my email address in the localepurge.8.patch file.

schivmeister commented on 2010-11-14 10:53 (UTC)

Ahh OK. Anyway I wanted to bring this to [community], but I've decided it's best left here and under your care. So keep up the work with this :)

fgr commented on 2010-10-23 13:55 (UTC)

Updated PKGBUILD to apply the hint by schivmeister. Note: I'm going to update pkgrel (starting from 1) since a new upstream version will be released.

fgr commented on 2010-10-16 09:29 (UTC)

Hi schivmeister, sorry for the delay in replying. About first point: I haven't decided to release a fork of the localepurge original version. However, as you rightly say later in your comment, the GPL doesn't grant me permission to redistribute a work with another license. About second point: probably, I'll follow your hints. Thanks. > One final note is that I don't know whether your licensing is valid, since you are deriving GPL work. GPL dictates copyleft for derived works. The Gentoo adaptation of localepurge is also GPL. Why go through the trouble of changing the license (to an invalid one) when all you're doing is patching the program for redistribution? IMO, my license is like CPL <http://www.cypherspace.org/CPL/> or WTFPL <http://sam.zoy.org/wtfpl/>. Obviously, only my code is released with my custom license (that is for my patches). Just a note about my license: I think the GPL is not truly free. Moreover, it doesn't reject intellectual property. I don't give a damn about some silly laws. My license hasn't approved by any institutions or state laws. It's just for this that, IMO, one is very permissive. And people aren't able to use the law to enforce the rights given by the license. But this is philosophy and off topic here.

schivmeister commented on 2010-10-12 16:56 (UTC)

Hello One thing: the copyright notes on the debian page tells me this is GPL software. Why is the license here custom? edit: nevermind..i see this is your own patched tarball it's downloading. edit2: you can go 2 ways.. 1) You should just pre-patch the files and release the tarball. In this case you would be "upstream". So the PKGBUILD should only need to move files around. As you would be deriving an existing work, you are free to bump or add revision numbers. A "localepurge-arch-0.6.2_$customrel" looks good to me and the underscore is friendly with our package management (ie. $pkgver). OR 2) Release only your patches. The PKGBUILD should download the deb src or whatever it is that gives you the original files. It will also download your patches, and the steps would be pretty much the same as they are now. If your patches change, there will be pkgrel updates only. One final note is that I don't know whether your licensing is valid, since you are deriving GPL work. GPL dictates copyleft for derived works. The Gentoo adaptation of localepurge is also GPL. Why go through the trouble of changing the license (to an invalid one) when all you're doing is patching the program for redistribution?