It turns out that if Python is updated, my package will not work, and I want to install it in a different folder, for example
"usr/lib/${pkgname}/" or "opt/${pkgname}/"
This is intentional. If there's a new major python version released, all python packages need to be rebuild.
but no matter what I do, the package is still installed in the folder
$pkgdir/usr/lib/python3.8/site-packages/$pkgname directory.
That's where it belongs.
]]>$pkgdir/usr/lib/python3.8/site-packages/$pkgname directory.
It turns out that if Python is updated, my package will not work, and I want to install it in a different folder, for example:
"usr/lib/${pkgname}/" or "opt/${pkgname}/"
but no matter what I do, the package is still installed in the folder:
$pkgdir/usr/lib/python3.8/site-packages/$pkgname directory.
]]>Is non-working.
Aside from the aforementioned PKGBUILD documentation, see also: https://wiki.archlinux.org/index.php/Py … guidelines
]]>man PKGBUILD
and of course, the wiki page
]]>Secondly, as far as I know, you're not supposed to use full paths in that way, as the command would directly install to /usr/lib, creating files not tracked by Pacman that may cause conflicts down the road. That's what ${pkgdir} is for.
The fact you're getting an error when it runs that command makes sense - you're trying to write to a system location as a normal user.
My option:
```
build() {
cd "${srcdir}/cine-encoder-${pkgver}"
python setup.py install --install-dir="/usr/lib/${pkgname}"
}
```
Is non-working.
]]>