Package Details: gist-lite 0.9-1

Git Clone URL: (read-only, click to copy)
Package Base: gist-lite
Description: Bash script for gist management
Upstream URL:
Keywords: bash gist
Licenses: GPL3
Submitter: typebrook
Maintainer: typebrook
Last Packager: typebrook
Votes: 1
Popularity: 0.000000
First Submitted: 2020-05-10 16:34 (UTC)
Last Updated: 2020-07-14 14:23 (UTC)

Latest Comments

glitsj16 commented on 2020-05-13 18:03 (UTC)

@typebrook Thank you for taking the time to consider the suggestions. I really like managing gists this way. Everything is working as expected, so i agree it's good to go.

All the best and take care!

typebrook commented on 2020-05-13 17:06 (UTC) (edited on 2020-05-13 17:07 (UTC) by typebrook)

@glitsj16 You are totally right.

In ArchWiki pacman page, the section about conflicting files already says bug report is needed if the file is owned by another package. Which implies install file owned by another package is disallowed.

Latest version 0.4 just install script as gist-lite, and changes helper message by current script name. It also shows the hint about how to alias it into gist, a shorter name used by Upstream. So now I think this package is good to go!

typebrook commented on 2020-05-13 03:05 (UTC)

@glitsj16 Many thanks for your feedback!
Looks like the Creating & Modifying Packages forum is the right place where I can get the answer and review for my PKGBUILD. I will make a post there later for this issue.

Have a good day!

glitsj16 commented on 2020-05-12 19:44 (UTC) (edited on 2020-05-12 19:46 (UTC) by glitsj16)

Hi @typebrook, I had a look at the new PKGBUILD. Here are my observations.

(1) You will have to install the script as gist-lite, or more exactly, as whatever name you prefer except 'gist', to avoid colliding with the ruby script from AUR and community. This is not an option I'm afraid. Even when a user doesn't have the gist or gist-git package installed at the moment they install this package, it will cause name-collisions the moment they will try to later on. This implies the package() function in PKGBUILD will have to be changed back again, only changing the name of the script in /usr/bin.

(2) That bash script itself needs minor editing. It only needs to reflect the name change discussed above in (1). But again, this is not optional in my opinion. If a user looks at the 'help' command and is informed that running 'gist fetch' will update the local gists and runs that command, it will not do the expected thing if the ruby 'gist' script exists at runtime. Things will break, on both sides.

I understand that you didn't want to touch helper messages and the README at this moment. I also hope the above clarifies why this will have to be done anyway because of the naming collision. Please note these are just my personal opinions, and not in any way 'official'. The best thing you can do is to contact Arch Linux staff via the available channels listed below.


Creating & Modifying Packages forum

aur-general mailing list

IRC channel #archlinux-aur: ircs://

typebrook commented on 2020-05-12 16:26 (UTC) (edited on 2020-05-12 16:28 (UTC) by typebrook)

Hi @glitsj16

package is updated and I add an option for user if community/gist is installed:
1. install script as gist-lite
2. abort installation
3. let user name the script

I guess it would be better do not touch helper message or README now.
Please take a look and tell me how you think, thanks!

glitsj16 commented on 2020-05-12 03:47 (UTC) (edited on 2020-05-12 03:48 (UTC) by glitsj16)

@typebrook Thanks for your speedy response! I'm not sure whether installing it as /usr/bin/gist-lite would be all that needs to be done to avoid collisions. The refers to 'gist' in all the examples. Those would have to be changed accordingly I guess, which might be a bit of extra work for you. But alas that's the only way I can see both packages running happily side by side on Arch.

Actually I am new to AUR, is there any convention to deal with naming collision like this?

If there are conventions like that, I'm afraid I am not familiar with them. It happens I was on IRC and asked around there just now. If anyone answers with relevant info, I'll post it here. Fine package though, I hope you can sort things out soon!

typebrook commented on 2020-05-12 03:22 (UTC) (edited on 2020-05-12 03:24 (UTC) by typebrook)

@glitsj16 Thanks for your feedback!

Unfortunately, there's already a community package called gist

I know this, so I named this package as gist-lite

Would you be willing to adjust this package?

I am not sure... because in helper message the command is just called gist. Should I install it as /usr/bin/gist-lite?

Actually I am new to AUR, is there any convention to deal with naming collision like this? If there is or you have another suggestion, then I will follow it to adjust this package.

glitsj16 commented on 2020-05-12 03:10 (UTC) (edited on 2020-05-12 03:48 (UTC) by glitsj16)

Hi, looking at this looks like something I'd want to use. Unfortunately, there's already a community package called gist that comes with a /usr/bin/gist as well. So in its current state the PKGBUILD for gist-lite collides with that. Would you be willing to adjust this package?