Open ganto opened 6 years ago
If the original author does not reply, there is always the option to fork the project and go from there.
You may have seen the number of issues here: https://github.com/open-sw/pkg-cacher/issues They are all opened by me or @brianjmurrell, a former coworker of mine. If you were to take the project and actively develop it, he would probably be pretty happy about it, as I believe he still actively uses this project.
That's a Texas-sized 10-4!
Hey there, I'm sorry but I'm in the process of moving so I'm a little preoccupied. Let me read over this thread and I'll get back to you.
| From: "Brian J. Murrell" notifications@github.com | To: "open-sw" pkg-cacher@noreply.github.com | Cc: "Subscribed" subscribed@noreply.github.com | Sent: Friday, March 2, 2018 11:26:14 AM | Subject: Re: [open-sw/pkg-cacher] State of maintenance of pkg-cacher (#38)
| That's a Texas-sized 10-4!
| — | You are receiving this because you are subscribed to this thread. | Reply to this email directly, [ | https://github.com/open-sw/pkg-cacher/issues/38#issuecomment-370026496 | view | it on GitHub ] , or [ | https://github.com/notifications/unsubscribe-auth/AFmhHYblTHKL_VH-TrY3-w5dXBNgOTZRks5taZzWgaJpZM4SZc1Z | | mute the thread ] .
Wow, what a response in less than a day. Seems that there are still some people beside me loyal to pkg-cacher. :+1:
If the original author does not reply, there is always the option to fork the project and go from there.
@jkugler That would be a bit more than I would be willing to invest into this. I don't see it included in any major distribution (anymore) and I'm not sure how many other users there still are except the one's already replied now. I'm also not so familiar with perl. I simply fixed some issues that I found and refreshed the packaging (because I like to). I'm happy to contribute it to upstream, so everyone can benefit. But if no one would have replied, then those changes would just happily life in my Github fork.
You may have seen the number of issues here
Sure, I saw. Unfortunately, I haven't experienced any of those by myself, so I didn't look into them in detail. I also experienced some minor (cosmetic) issues where I'd like to look into the code a bit more, but first I wanted to get everything else sorted.
Let me read over this thread and I'll get back to you.
@Robert-Nelson Sure, take your time. I would also offer you to help co-maintain this, as how I said I still have several setups where I happily use pkg-cacher on a constant basis.
@Robert-Nelson
Hey there, I'm sorry but I'm in the process of moving so I'm a little preoccupied. Let me read over this thread and I'll get back to you.
Any update on this?
Since many years I'm using pkg-cacher as a caching proxy in my internal network and especially on my laptop to have a offline cache when I'm commuting. For the past few years I used a carefully crafted Docker container linuxmonk/pkg-cacher which exactly fit my setup. In the meantime they way how container should be built to be usable with all the different orchestrators did shape up and it became one of the expected deliverables of an open source project to also offer the software in a container. However, for the reporting feature to work in a modern container, this would need some code changes which I might eventually have a look at.
With this background I cleanup my various pkg-cacher bug fixes and enhancements so that they could easily be submitted as individual PRs (see my branches). It's nothing big, mostly updates to the
.regexp
files and a refresh of the Fedora spec and Debian maint files. All updates with some value for upstreaming are combined in the ganto/pkg-cacher:contrib branch.I see that there is no more activity on your Github profile since a while and no more commits or merges in this repository since nearly 3 years, are you still maintaining this project? Would you have a look at my changes if I open PRs for them?
Btw. if someone is interested in a "proper"
pkg-cacher
docker container, checkout linuxmonk/pkg-cacher-docker which is built from the ganto/pkg-cacher:docker branch.