SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hey all,
I'm wondering if there is a way to see all the SlackBuild packages that do not currently have maintainers. I've written my first package, it was accepted, and I'm thinking taking over maintenance of some others might be a way I can actual contribute to the community (since I'm more of a user right now then a dev).
It seems that just a search on SB for "unmaintained" does not get any hits, so the search is likely not going through the README files (or something). Anyway, is there a simple way of seeing the packages without current maintainers?
Orphaned packages are one of the most frequently discussed matters on the SlackBuilds-users mailing list. Right now they're discussing Marcel Saegebarth's orphaned builds and who is willing to take over what. I'd strongly recommend subscribing and speaking up when you see a project you'd like to assume.
Orphaned packages are one of the most frequently discussed matters on the SlackBuilds-users mailing list. Right now they're discussing Marcel Saegebarth's orphaned builds and who is willing to take over what. I'd strongly recommend subscribing and speaking up when you see a project you'd like to assume.
Yeah this is great, this is exactly what I did.
So now I can see there is a list of old packages that are "on the cusp", so I'd like to take over a few.
I'm not sure if anyone is actually on that list here, but now that I've joined I want to know how to respond to an old topic, so I can get my name on some of these. Anyone know how to do that?
Yes that's list I'm talking about now - they are discussing it on the SlackBuilds mailing list, but I don't know enough about how the mailing list works to respond to the relevant message and let them know which I'm interested in.
Thanks! :-) I was intrigued to see mrxvt appear there. It's one I use, and I am actively developing a fork of it called MisterX, so have some familiarity configuring/building it.
But then today someone on the list pointed out that the mrxvt SlackBuild -is- being maintained, and it shouldn't be on the list at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Unmaintained Slackbuild Packages
