-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing shutter crashes while determining deps #13
Comments
This is coming up a lot. I have theories.
I know for a fact my mini-parser wouldn't make sense of those extrapolated perl deps. Why this would result in an empty list error is beyond me, but I'll look into it. |
In PKGBUILDer, I give the dependency parsing job to bash itself. It is much easier and nicer. For example, my cheaty pyparsing solution required total magic, an AUR dependency for PB itself (and that is evil, and is currently limited to 2 for yours truly’s sanity, i.e. requests and certifi [requests dep], HTTP for Humans™) and broke when there were some problems, eg. source PKGBUILD; for i in ${depends[*]}; do echo $i; done; for i in ${makedepends[*]}; do echo $i; done (bash requires such fancy brac{e, ket} magic. In zsh, you can just do |
I use fish shell. Do you know how Does your solution there guarantee that the only things being read are the |
Nope. My method also sources the PKGBUILD ( |
And the day that the AUR gets hacked? |
Just a note, shutter goes even more apeshit now.
It might not like the fancy |
Nono, those \ are totally necessary. It's the {}. Bash would expand those, but aura isn't yet. This is the current biggest issue with aura. I'm debating on whether I should implement more manually hackish Bash parsing, or try and find a tool to do it that won't acutally RUN the script. |
Wrote a mini-parser to deal with bash expansions. Shutter builds now! |
I'm currently running into the following error when trying to install shutter from AUR.
The text was updated successfully, but these errors were encountered: