Package Details: windows10-icon-theme-git r14.9f199c6-1

Git Clone URL: (read-only, click to copy)
Package Base: windows10-icon-theme-git
Description: Windows 10 icon theme
Upstream URL:
Licenses: GPL3
Conflicts: windows10-icon-theme-git
Provides: windows10-icon-theme-git
Submitter: schrodinger72
Maintainer: zerophase
Last Packager: schrodinger72
Votes: 14
Popularity: 0.000271
First Submitted: 2019-05-02 21:17
Last Updated: 2020-10-23 17:11

Dependencies (1)

Required by (2)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

zerophase commented on 2019-05-02 21:10

@sangy @eschwartz Sure. Would using git+git:// be preferable for avoiding the https / ssh issue?

I was initially angry over the package getting reported a few months ago for being broken, and one of the other maintainers closed the issue out of the package being packaged perfectly fine. I'm just confused since I have not had this much animosity towards other packages involving ssh.

sangy commented on 2019-05-02 20:56

Hi @zerophase. Please keep your conversation civil when interacting with other members of the AUR community. Disrespectful behavior can warrant an account suspension.

eschwartz commented on 2019-05-02 20:53

Hi, this is a Trusted User and maintainer of the AUR speaking. Please stop using ssh, or the package ownership will be forcibly removed from you and transferred to someone who is willing to package in a manner that respects other users.

Also, your rudeness is completely unwarranted.

zerophase commented on 2019-05-02 16:55

@fwhcat No, the link points to the main product page. If you want a different version of the pkgbuild write a custom pkgbuild. Sign up for a github account, or fuck off and stop trying to steal the repo since a decision I made is inconvenient to someone blocked from github. No, ssh is a current standard, learn it or role a custom repo with one line edited.

schrodinger72 commented on 2019-05-02 14:56

btw, you changed source link but not url link. This should be changed to : as well.

I understand you prefer ssh, but people don't necessary have a github account, and the advantage of the https link is that everyone can retrieve it. You use ssh to maintain your packages, sure, but that is a different thing than retrieve the files for people to install your package.

So, yes. You should definately take suggestions from people who are willing to make this a better experience for everyone.

schrodinger72 commented on 2019-05-02 14:34

https clone doesn't require any login if your repo is public.

zerophase commented on 2019-05-02 12:53

I prefer ssh. So, my packages stay ssh based as it is the least hassle for me to maintain, and my system install scripts use ssh. It's not my problem you are unwilling to sign up for a github account and generate an ssh key pair for it. You still need to put a password in anyways if it is https. I could try switching to git+git when I have the time.

Definitely, not taking any suggestions from someone trying to report my repo as orphaned.

zerophase commented on 2019-01-05 21:33

@jtmb I'm sure it can be. Github asked me to login when I tried https. (probably since I clone with ssh usually) so, I just used ssh to avoid having to manually login sometime down the line. Let me look at my github settings, and see if there's something I can conveniently tweak there.

I will be requesting this repo get merged to git repo in the near future once once I'm sure the package build handles the switch correctly.

jtmb commented on 2019-01-05 21:06

@zerophase any reason this can't be git cloned with https?

zerophase commented on 2018-12-30 17:55

@PauleBerline Yeah, sign up for a github account and setup your ssh key on your local machine.