[SOLVED]AUR with pip problem

kynguyen98 · 2020-04-19 15:31:07

So I created my first AUR package that uses pip to install my software with other dependencies but whenever I uninstall the software with regular pacman it did not remove them, I have to use pip again to uninstall it. Am I dumb to use AUR that uses pip while pip is a package installer or AUR didn't compatible with pip
Here is my code again I'm new so don't judge my build, please

pkgname=stm32pio
pkgver=1.0.1
pkgrel=1
#epoch=
pkgdesc="Automate managing STM32CubeMX + PlatformIO projects" 
arch=('x86_64')
url="https://github.com/kynguyen98/stm32pio"
license=('MIT')
#groups=()
depends=(python-pip python jre8-openjdk)
makedepends=(git python-pip)
#checkdepends=()
optdepends=('code: for text editing')
#provides=(stm32pio)
#conflicts=()
#replaces=()
#backup=()
#options=()
#install=
#changelog=
source=($url"/archive/v${pkgver}.tar.gz")
#("$pkgname-$pkgver.tar.gz""$pkgname-$pkgver.patch")
#noextract=()
md5sums=('SKIP')
#validpgpkeys=()

#prepare() {
#	cd "$pkgname-$pkgver"
#	patch -p1 -i "$srcdir/$pkgname-$pkgver.patch"
#}

#build() {
#	cd "$pkgname-$pkgver"
#	./configure --prefix=/usr
#	make
#}

#check() {
#	cd "$pkgname-$pkgver"
#	make -k check
#}

package() {
	cd "$srcdir/$pkgname-$pkgver"
#    cd src/stm32pio-1.0
#	make DESTDIR="$srcdir/$pkgname-$pkgver" install
	make install
#    make install --root="$pkgdir/" --optimize=1
}

Last edited by kynguyen98 (2020-04-19 17:15:09)

Trilby · 2020-04-19 15:36:55

So you ran pip as root and installed a bunch of python tools circumventing pacman. Yes, this was a very bad idea.

You seem aware already that you need to remove these with pip, so I'm not clear what you are asking. Your only actual question was "Am I dumb" ... do you want an answer?

General PKGBUILD notes:
- That PKGBUILD does almost nothing, and what it does do is wrong. It creates an empty package, effectively a meta package with some dependencies ... which aren't actually dependencies of the tool you wanted to install
- All the commented lines are highly distracting, get rid of them
- Arch should be any, nothing is compiled
- Python-pip would be a makedepends, but you have it as both make and regular depends. If a package is in the depends array, it should not also be in makedepends. Of course in this case, it shouldn't be there at all.
- Git is listed as a makedepends, but git is never used. Get rid of git.
- 'Code' as an optdepends is ridiculous. A text editor many be an useful, but there is absolutely no reason to just list your favorite one there.
- Do not 'SKIP' checksums for static sources
- You commented out a proper make call using DESTDIR. The fact that your makefile would ignore DESTDIR should have been a red flag. Your package function does not install anything into $pkgdir, so it results in an empty package.

EDIT: I just saw you also uploaded this to the AUR. If you are still learning, winging it and botching a PKGBUILD on your system is one thing, but please do not upload something to the AUR when it is clear you haven't even glanced at the proper documentation.

Last edited by Trilby (2020-04-19 16:05:32)

yochananmarqos · 2020-04-19 16:02:23

Please see Python package guidelines and use your setup.py.

WorMzy · 2020-04-19 16:03:18

Mod note: Moving to AUR Issues

kynguyen98 · 2020-04-19 16:20:59

Trilby wrote:

So you ran pip as root and installed a bunch of python tools circumventing pacman. Yes, this was a very bad idea.
You seem aware already that you need to remove these with pip, so I'm not clear what you are asking. Your only actual question was "Am I dumb" ... do you want an answer?
General PKGBUILD notes:
- That PKGBUILD does almost nothing, and what it does do is wrong. It creates an empty package, effectively a meta package with some dependencies ... which aren't actually dependencies of the tool you wanted to install
- All the commented lines are highly distracting, get rid of them
- Arch should be any, nothing is compiled
- Python-pip would be a makedepends, but you have it as both make and regular depends. If a package is in the depends array, it should not also be in makedepends. Of course in this case, it shouldn't be there at all.
- Git is listed as a makedepends, but git is never used. Get rid of git.
- 'Code' as an optdepends is ridiculous. A text editor many be an useful, but there is absolutely no reason to just list your favorite one there.
- Do not 'SKIP' checksums for static sources
- You commented out a proper make call using DESTDIR. The fact that your makefile would ignore DESTDIR should have been a red flag. Your package function does not install anything into $pkgdir, so it results in an empty package.
EDIT: I just saw you also uploaded this to the AUR. If you are still learning, winging it and botching a PKGBUILD on your system is one thing, but please do not upload something to the AUR when it is clear you haven't even glanced at the proper documentation.

Yeah sorry and thank you pointing out my flaw I'll try to do more research about this

kynguyen98 · 2020-04-19 20:19:05

Thanks guys for letting me know my flaws in the PKGBUILD I have updated my build

Last edited by kynguyen98 (2020-04-19 20:19:36)

Trilby · 2020-04-19 21:00:08

And you uploaded it to the AUR again after only addressing a few of the critiques.

I can acknowledge that you did address a few of them very well, but you seem to have stopped half way.

In addition to the points in my previous post, the current package is missing the license file and the source download name is not unique (see the big red warning box under the "source" section of the wiki page on PKGBUILDs).

Last edited by Trilby (2020-04-19 21:19:31)

Arch Linux

#1 2020-04-19 15:31:07

[SOLVED]AUR with pip problem

#2 2020-04-19 15:36:55

Re: [SOLVED]AUR with pip problem

#3 2020-04-19 16:02:23

Re: [SOLVED]AUR with pip problem

#4 2020-04-19 16:03:18

Re: [SOLVED]AUR with pip problem

#5 2020-04-19 16:20:59

Re: [SOLVED]AUR with pip problem

#6 2020-04-19 20:19:05

Re: [SOLVED]AUR with pip problem

#7 2020-04-19 21:00:08

Re: [SOLVED]AUR with pip problem

Board footer