Is there a way to learn the development model of slackware?
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.
Is there a way to learn the development model of slackware?
Hi, all:
I am a slackware user from slackware 9.1, these years I tried many distributions, but slackware always winner. I am familiar with server configuration and desktop setup for slackware, but I know nothing about the development model of slackware, is there a way to learn the development model of slackware?
Like, freebsd, you can checkout the kernel source, tool chains source from cvs then build it, some people will commit and check in the change sets, they have a mailing list for developers to talk about the development, for users to learn what are they doing now.
I know there are many README or Documents for slackware, but I donot know anything about internal development, is there a way? a mailing list? a source repository(cvs/git or others?)
What is Slackware's development model?
* Commercial distribution, funded only by store sales. On the other hand, forever free to download.
* Non-open development
--- No bugzilla, no public code repository, no code contributors
--- No procedures to "become" a developer.
* "Benevolent Dictatorship" (although Pat would not agree).
The final decision about what goes into Slackware remains with Patrick Volkerding. But... he listens to common sense.
* Not a one-man show!
Slackware has a core team of contributors
--- Non-public testing of new, or updated, packages
--- Contributing changes to Slackware core scripts (bootup, network, installation, ...)
--- Proposing for new packages to be added
--- Providing a private discussion forum to decide on future steps
Have a look at the slackbuilds for alien bob's 64 bit add-on, as this will give you some information on creating a toolchain, also de-compress the initrd.img in the /isolinux directory of the install media that you use. Studying this will give you an idea of how the boot process works, and allow you create your own version. You could also look for an old article called "cooking up some slack".
Thanks for all your replies, I never know that Slackware is "Commercial distribution, funded only by store sales. On the other hand, forever free to download.". But I think that's not problem.
I will try to find more information from bob's site.
Like, freebsd, you can checkout the kernel source, tool chains source from cvs then build it, some people will commit and check in the change sets.
a source repository(cvs/git or others?)
Thanks very much.
In addition to ponce's reply, Slackware has a source tree for all supported versions on all mirrors (and on the DVD and CDs no 4,5 & 6). Pat is the only who commits changes to it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.