Program is no longer maintained #1

Closed
rg3 opened this Issue Feb 19, 2015 · 4 comments

Comments

Projects
None yet
4 participants
@rg3
Owner

rg3 commented Feb 19, 2015

Recently, I moved away from Slackware. I'm still using it in a couple of boxes here and there, but it's no longer present in my main system. This means the program will eventually bitrot as I'm no longer using it. In any case, Slackware doesn't change much over time. It should be safe to continue using slackroll at least until the mirror structure changes, or until Python 3 becomes the default version.

@aadityabagga

This comment has been minimized.

Show comment
Hide comment
@aadityabagga

aadityabagga Mar 6, 2015

I just discovered slackroll after someone posted on the forums; seems like an interesting tool so far :)

I just discovered slackroll after someone posted on the forums; seems like an interesting tool so far :)

@Gunbird

This comment has been minimized.

Show comment
Hide comment
@Gunbird

Gunbird May 22, 2015

That's too bad. Slackroll is still the best packet manager for slackware in my opinion.

Gunbird commented May 22, 2015

That's too bad. Slackroll is still the best packet manager for slackware in my opinion.

@ryanpcmcquen

This comment has been minimized.

Show comment
Hide comment
@ryanpcmcquen

ryanpcmcquen Jan 19, 2017

What OS did you move to?

What OS did you move to?

@rg3

This comment has been minimized.

Show comment
Hide comment
@rg3

rg3 Jan 21, 2017

Owner
Owner

rg3 commented Jan 21, 2017

aclemons added a commit to aclemons/slackroll that referenced this issue Jan 23, 2018

@rg3 rg3 closed this in b4208ab Jan 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment