[aur-general] Merge request: python2-pyside -> python-pyside
Hugo Osvaldo Barrera
hugo at osvaldobarrera.com.ar
Thu Sep 19 05:38:21 EDT 2013
On 2013-09-16 05:43, Xyne wrote:
> Hugo Osvaldo Barrera wrote:
> >As maintainer of python2-pyside shouldn't I have gotten a notification
> >about this? At least an automated one from the AUR?
> >Also, since the PKGBUILD states "replaces=(python2-pyside...", shouldn't
> >searching the AUR for python2-pyside yield python-pyside as one of
> >the results?
> The AUR does not fully parse PKGBUILDs because that would require a tool that
> can fully parse Bash without executing it, which no one has written yet (to my
> knowledge). As such, the current approach fudges it with simple regexes or
> whatever that only extract a subset of data. I do not think that includes
> The AUR also lacks true support for split packages (again, because there is no
> full Bash parser*), which is why the python2-pyside split package is not
> >Finally, why does this merge make sense? It merges two *different*
> >libraries into one; I maintained python2-pyside, but have no interest
> >in installing the python3 version, so why is the original package deleted?
> A split package builds 2 or more packages. You may optionally install any of
> them as needed. It makes sense here to have a split package because both the
> Python 2 and Python 3 versions are built from the same source. The only
> argument against having a split package in this case is the lack of AUR
> support, which makes the package a little harder to find and which requires
> some ugly hacks to the PKGBUILD (e.g. "true &&" to trick the parser).
> * This is the price we pay for having all metadata trapped in a general
> purpose, quirky scripting language that can only be evaluated by executing
> arbitrary code.
But AUR helpers don't really process there split packages either, so
they only benefit people that will manually download and install them,
and even those cases, the new package builds both the python2 and python3
I guess my real question is: do we really want to delete python2-pyside
from AUR? If so, why? The fact that two packages use the same source
doesn't seem enough, IMHO (we have plenty of variations of the same
package in aur already).
Hugo Osvaldo Barrera
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 490 bytes
Desc: not available
More information about the aur-general