Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
okay , so you mean some ordinary bash scripts or something like Makefiles ?
well i remember that slackware doesn't use rpm , so i guess you're talking about binary tarballs, right ?
Yeah they use bash scripts, sorry I should have been a bit more clear on that one. I think rpm's might be a binary tarball as well, just a different type, I can't be 100% on that though. Slackware have all the scripts used to build each package in the source directory on the disc or source directory where you download it from.
That way you can change a few things in each of the script to suit your requirements, and then do a complete rebuild of all the packages.
I did at one stage make a bash script to go and find all the scripts, change what I needed, then go through each directory and run the scripts to remake all the packages. If you want to make your own distro, this would be an easy way to do it.
I mean DebianLive. Google it and read up on it you will find it interesting.
well it's a live distro , what a surprise...
i'm not quite sure how that is irrelevant , btw i've read some of its docs on the official website , which does mention commands for compiling it but it doesn't talk about the technology behind it ...
i'm not interested in any particular distro instead i'm interested in the methodology used to compile them.
Quote:
Slackware have all the scripts used to build each package in the source directory on the disc or source directory where you download it from.
good to know.
however i'd exempt slackware from the question above , since it's rather simplistic and uncomplicated from a development perspective.
i doubt though that large distros such as ubuntu , fedora, opensuse rely just on simple scripts to compile thousands of packages.
now i'm aware that large distros unlike slackware are package managed through things like rpm.
although rpm is great for single packages , it isn't enough for packaging distros.
so a clearer question would be : what rpm(or whatever package management system is used) supplement is needed in order to build and package the large mainstream distros ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.