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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm looking for an efficient way to set up a custom repository for Slackware packages. I'm planning to maintain a mixture of customized 'stock' (optimized CFLAGS, without PA depedendencies, etc.) packages and a few of my own.
What's the best way to accomplish my goal? I'm not looking for in-depth tutorials here but more of a general guidance on best practices, etc.
I'm also looking for a way to automatically track and download all updated Slackbuilds from the official Slackware mirrors and then automatically change the CFLAGS if needed. What would be the best way to accomplish that? Any recommended tools for this kind of job?
Also, do you know about the SlackOnly project (https://slackonly.com/)? Might interest you, it aims to provide packages compiled from the scripts at SBo.
I'm looking for an efficient way to set up a custom repository for Slackware packages. I'm planning to maintain a mixture of customized 'stock' (optimized CFLAGS, without PA depedendencies, etc.) packages and a few of my own.
What's the best way to accomplish my goal? I'm not looking for in-depth tutorials here but more of a general guidance on best practices, etc.
I'm also looking for a way to automatically track and download all updated Slackbuilds from the official Slackware mirrors and then automatically change the CFLAGS if needed. What would be the best way to accomplish that? Any recommended tools for this kind of job?
Thanks in advance.
I'm maintaining my own repository with roughly 1.300 packages and counting. I'm building my stuff in a series of KVM guests. Metadata is created with Eric Hameleers' nifty gen_repos_files.sh script. Then I'm uploading the stuff to a public server.
Also, do you know about the SlackOnly project (https://slackonly.com/)? Might interest you, it aims to provide packages compiled from the scripts at SBo.
Slack Only is looking for volunteers if you are interested.
Also, do you know about the SlackOnly project (https://slackonly.com/)? Might interest you, it aims to provide packages compiled from the scripts at SBo.
iirc there was a command line tool a la slackpkg covering third party repos (slackonly, alienbob), does anyone know the name?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.