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.
If you don't like that, it means you were insincere about your intentions to "just ask".
Oh sorry it seems that I haven't made it obvious in my header subject that I'm somehow wanting to know the opinion of the Slackware team themselves. You know the answer, because you're one of the representatives? Or do you expect it? How different is that to how I estimate that it could be likely that it would be rejected? Even I so I try for I know there's a valid point in it somehow.
Oh sorry it seems that I haven't made it obvious in my header subject that I'm somehow wanting to know the opinion of the Slackware team themselves. You know the answer, because you're one of the representatives? Or do you expect it? How different is that to how I estimate that it could be likely that it would be rejected? Even I so I try for I know there's a valid point in it somehow.
Oh, and your meaning is that you did not want to hear from anyone else? Then you shouldn't have posted here at all. You should have contacted them directly.
@Didier Spaier I don't really see the need of having another dedicated team to just rebuild what's already in a dvd after a stable release to have another dvd that's optimized for a specific CPU type, most basically the ones that could be provided to march or mtune.
To be sure that you measure the amount of work that would need, I suggest that you do it yourself for only one CPU type.
To be sure that you measure the amount of work that would need, I suggest that you do it yourself for only one CPU type.
The fact that Slackware packages are built individually, and there's no automated process to build them all at once, obviously makes this proposal even more difficult to implement.
Oh, and your implication is that you did not want to hear anyone else? Then you shouldn't have posted here at all. You should have contacted them directly.
I made a choice to ask in a bit more casual manner like in this forum rather than bothering them directly. As for other people's opinion I am open to it. And I mean opinion, not affirmations.
As for other people's opinion I am open to it. And I mean opinion, not affirmations.
You asked a yes/no question. The answer is no. I'm not going to pretend that it's not the correct answer just because you're not open to "affirmations". That is not my problem.
The fact that Slackware packages are built individually, and there's no automated process to build them all at once, obviously makes this proposal even more difficult to implement.
I wonder. I actually see it to be only a script or two. If they already have something that automates the build of one release, changing the flag for it would just be easy.
@TobiSGD I know the possibility of re-building Slackware certainly. But it's better if it's already provided and ready for download. And an official package is also irresistible to take, and probably collect or archive.
konsolebox, do you know that slackware is maintained by just one person?
I think you are missing this very important detail related to what you're asking for (and that is the reason of my previous post).
I wonder. I actually see it to be only a script or two. If they already have something that automates the build of one release, changing the flag for it would just be easy.
They don't.
There is one script per package. Packages are updated and rebuilt on an individual basis in the process of developing the -current branch. A release is just a snapshot of -current. In a typical release, many packages will have not been rebuilt or updated since the previous release.
Yet that automation script could be made if it's not yet there if they decided to. It's pretty easy I think. As an example, even with the known utility src2pkg we could just have a list file or a formatted file of packages that could be parsed and call the utility continuously. Stop somewhere if it fails. Log redirections with tee -a. It's fairly easy actually. And it's rare for a build to fail just because a cpu type is changed.
Yet that automation script could be made if it's not yet there if they decided to. It's pretty easy I think. As an example, even with the known utility src2pkg we could just have a list file or a formatted file of packages that could be parsed and call the utility continuously. Stop somewhere if it fails. Log redirections with tee -a. It's fairly easy actually. And it's rare for a build to fail just because a cpu type is changed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
