Deprecated archey-omz-git

[WildCryptoFox]

Hello,

I'm unsure as to what happened to the repository, and I'm sorry to say that it had been deleted. Do you still use the old code?

Alternatively you might want to switch to: https://github.com/sorin-ionescu/prezto/

Cheers, James.

[zancarius]

I switched to oh-my-zsh some time ago but left this in my repository, mostly because I'm just really forgetful. Sorry about that.

I'll go ahead and remove it. It'll give me a chance to clean things up a bit.

Thanks!

[WildCryptoFox]

Thanks!

[zancarius]

Okay, I moved it to my DEPRECATED section, mostly because I didn't have the heart to remove it just yet. I need to go through those packages and (eventually?) decide what I want to keep.

To answer the comment you made earlier that for some reason isn't showing up here (edited?) but did appear via the Github mail: No, I haven't used Freenode in a long time. I probably have the password somewhere. I've never been much of an IRC junky, and after the weirdness Freenode had about a year or two ago I haven't had much interest returning.

Problem is that I can't decide if it's because I'm somewhat anti-social or lazy. It's like the joke: "I always used to be so undecided. Now I'm not so sure."

:)

[zancarius]

I'm going to close this for now. If you reaaaaaally want me to delete the package (or anything else you think might be too stale), feel free to continue commenting or make a new issue.

[zancarius]

I used to use IRC with some varying degree of regularity probably some 15+ years ago (this might date me a bit). Mostly EFNET, and mostly because I used to enjoy 1) trackers (the music variety), 2) stupid IRC debates, and 3) instant messengers hadn't completely caught on (though they were growing). Not quite sure why I lost interest, but there's a reason in there somewhere. :)

Odd that the registered date was showing up then. IIRC, I actually used Freenode for a year or two. Maybe my recollection is off a bit, but I have a BitchX configuration file that dates back to a number of years ago, and I'm fairly sure I used it off and on for sometime thereafter.

[zancarius]

I'm aware of how git works. I use it regularly for my own projects. Don't be so naive as to assume a project structure was chosen due to ignorance over laziness. :)

There's a reason I created a deprecated folder, probably because I wanted to keep the packages in the working tree. I'm not quite sure why I didn't create a branch for that alone, but I suspect it had to do with some scripts I'd written for handling AUR-related cruft.

[zancarius]

Possibly true, but this is an assortment of PKGBUILDs. It doesn't really matter, and since I'm the only one who bothers with it, fussing over the structure is akin to splitting hairs--what's the point?

Besides, all AUR4 packages are now themselves handled by Git on the Arch side of things, so aside from having a singular area I can stuff all of my work (along with issue tracking, etc.), one could reasonably argue there's no reason for this repository to exist either. And once they support branches in the aur code (or issue tracking themselves), I might even be so inclined as to remove this entirely. No point duplicating effort.

Incidentally:

[gridlock:oh-my-zsh]$ cat .git/config
[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        fetch = +refs/heads/*:refs/remotes/origin/*
        url = https://github.com/archeydevil/oh-my-zsh.git
[branch "master"]
        remote = origin
        merge = refs/heads/master

It appears in my PKGBUILD directory that I still have your original repository.

Oh, that's right. Work-in-progress intermediate build directories (pkg, src) that I have added to my .gitignore file might be the reason why I didn't want to bother with removing some of these outright (or moving them to another branch). One, I didn't want to pollute my repository with them, and two, I probably didn't want to delete them either.

[zancarius]

Former Gentoo user here, oddly enough. Actually, before that it was OpenBSD -> FreeBSD -> Gentoo then finally Arch. (I use/have used Ubuntu for some purposes, but I'm not much of a fan of Debian-based distros--nothing against them, they work well, I just don't like them.)

I mostly dumped Gentoo because of the fun that was re-compiling glibc, xorg, KDE, etc., and I never really trusted pre-built binary packages since sometimes the repositories would either disappear or there'd be weird breakage--and finding a good overlay was, on occasion, painful. But that experience goes back some time ago (I migrated to Arch around 2011-2012). I still have a couple Gentoo VMs running to keep myself dabbling in it from time to time, and some of the recent changes have been quite nice, but nothing exceptional. Even my home router/fileserver box runs Arch, but that's mostly because I'm really lazy and prefer some homogeneity among my systems where appropriate or possible. Though it persisted as a Gentoo install well into 2013, IIRC.

While I'm in the mood for embarrassing (or maybe not so embarrassing) confessions: If I were to ever dump Arch, I'd go back to Gentoo before anything else. I have fond memories of Gentoo. It was my first Linux distribution and the one I think is most similar to the *BSDs in its philosophy and design.

AUR4 is a nice change, and it's why there's a lingering sense in my mind that Github PKGBUILD repos may eventually go the way of the dodo. Updates are just a git push, but you have to do some magic with mksrcinfo so their pre-commit-hook parsers, AUR front end, and undoubtedly other machinery can know what to do with the changes (as I understand it, that's mostly limited to versioning and other things the AUR software likes). I saw on the mailing list some time back that there's ongoing discussion regarding branches. I don't know what will come of it or if it's already in the works, but I have a very strong suspicion that branching will be added. If that's the case, other features are almost assured.

Already, due to the migration, my local copy of this repo has gotten somewhat messier in layout (not so much function) since each PKGBUILD must be its own repository. I'm reluctant to do anything else with it (submodules, etc.) mostly due to the lack of AUR4-supported branches, but it's a work in progress, and I'm happy with what they've done. It's now possible to have co-maintainers on the AUR side and split packages are becoming much easier to deal with. Some of the slightly painful, repetitive nonsense has been cleaned up or removed, so that's another plus.

As far as your old repository goes, I doubt I'll do much with it. I'm an archivist at heart (such a confession, I'm aware, might lend some insight into my motives with this repo in particular), so I may keep it--it weighs in under 1MiB, so what's the point in deleting it?--but that's little guarantee for what may become of it. Besides, most of my time spent writing code is spent on a half dozen other things (not hosted here, thank you GitLab!), so my motivations, energy, and time wouldn't be of much use--and my experience with shell-related code (any of them) is admittedly rather limited.

I greatly appreciate the work you put into your own omz fork. "Arch-ificating" it made it much more useful to me, especially when I first started migrating from bash to zsh, and if you continued maintaining it, I would've remained a faithful user. As it stands, though, the oh-my-zsh-git PKGBUILD does well enough for me, provided I disable some of the more... obnoxious plugins.

Anyway, it's well passed my bedtime here in the 'States. It's been fun.

Cheers, mate.

[zancarius]

Any particular reason why you have an affinity for suggesting I delete my responses as well?

[zancarius]

I'm not especially concerned. Nothing I've written is particularly secretive, informational, or insightful. Boring, perhaps, is a better qualifier.

You're welcome to your own choices, of course, as I see you have.

Cheers.