Quote:
Originally Posted by TobiSGD
While -current is the latest and greatest in terms of what you get with Slackware, it is not the latest and greatest in terms of the software incorporated in Slackware. There are many older packages that do not get updated regularly in it. Calling -current bleeding edge is interpreting the term "bleeding edge" very loosely, IMHO.
|
Ok,...Lets see if you can get around this one ... (or, lets match wits...just for the fun of it, hehe
)
One: That was just a copy and paste job. I had seen it posted in one of the Slackware Sites. In the contents that it was written, it may have been written with that slightly sarcastic humorous way. This would allow your statement.
Two: But your use of the word or term, even entire phrase, that not all the software that is incorporated into Slackwares "repo" is kept current. Only select packages. As much truth to that statement there maybe, or may not be. I do not know. I no longer use Slackware. But, I will still stand up for it, and talk my way out of this one.
It is because of the unique way that Patrick Volkerding designed then created his interpatation of how a GNU/Linux operating system should/could be is very user friendly. Because, them that deside to take on this type of operating system have to have, and deservedly so, if not already a basic knowleadge of Unix, and like systems but if not, then indeed a strong desire to do so.
Therefore, to me, by just seeing how it is designed to be maintained, that it gives the user of this operating system full control over every aspect of the system. Whereas, others do not?
If ones software is not within the repo then Patrick Volkerding designed his GNU/Linux system above and beyon just keeping the ability to install software using the "old" conventional way, being Configure, make, make install. Which allows the user/maintainer of the operating system in question to install anything into his or hers OS.
He has created a system using the basic bash scripting language. Something every user of not only Unix/Gnu/Linux Operating System, but everything that ones operates should know. The Basics. One can either just jump on the horse they've never had any experience in ridding. Then learn the basics of how to control the animal, or gather information frist so he or she has a good basic understanding in how to control it in order to get it to do what he or she wants it to. The only limites being the limatation of the animals own inherited traits, and capabilities. This rings true with software, and the operating systems written to run said software as well.
The person, now being the operator of said operating system in question is only limited in what he or she can do with it in two ways. The first one is, reguardless of the knowleadge of the user to operate and or malnipulate the OS in question. Is the limitations that the author of the OS has allowed the operator to have. He can close off certain avenues that remove the owner/operators abiltiy to malnipulate the software to get it to do what he or she wants it to. Preventing said owner/operator from full access to all of the inherited capabilities of said software.
The second way the owner/operator is limited in what he or she can do with the animal or software having full access to all of its inherited capabilities is the owner/operaters own self. His or hers own knowleadge, or lack thereof along with his or hers own ablities to be able to use his or hers own mind adequately. Meaning that they either possess the ability to use methods that are applied to one aspect of an item to get said item to do what that person wants it to do, but to then be able to apply it to a different item and still get this other item to do what he or she wants it to.
Or, the ability is learned how to transpose knowleadge of how to get one item to perform operations using its inherited capabilities onto a different item to get it to perform operations using its own inherited capabilities using the same like methods. Because the two different items may seemly be different, but in fact they do share a common thread. They have like traits and inherited capabilities that may not be apperent to the untrained eye. One needs more then knowleadge on how to do so, but experience in doing so as well. One can be book smart in all areas of knowleadge but if they lack the abiltiy to apply said knowleadge then it does them no personal good. They can only share it in hopes that the other person can actually put it to use.
With what some of the others have done with their distro's is limited if not taken away from the owners/users of the software including the operating system. Which in fact is software as well. Their ablity to have full control over their software with the use of how their Distro's are maintained. Creating a system that the user develops a type of codependency disorder as a direct result by allowing themselves to rely on the other person, or persons to take care of them and their needs in relationship to their entire operating system they choise to use. Including all of the other software that is installed on it.
Some people that allow this to take place give up or lose thier abiltiy to deal with reality in a normal fashion. They become not only fearful and untrusting of others and what they have to offer, but at the same time they start, if they were not already this way, lose the ability to even rely on their own judgments to get the same task completed. In this instance, install software that they will or may need or like to use on their own open source operating system.
"I do not use or install anything that is not kept in my Distro's repo's." Statements such as that show a fear of the reality of how the world is. The world is full of pit falls. Stress is a result of it. Stress is a result of everything we do. It is ever present in our lives.
They that use such statments as I presented are showing a type of codependency disorder that no longer allows them to deal with stress properly. Perhaps due to their childhood.
Even though this is not a paper or writting on the tpoic is psychology. Psychology is everywhere as stress is. It is ever present even with the type of distribution of GNU/Linux a person chooses to use. Persons that want a "Bleeding edge" distribution of GNU/Linux give themselves away as to what type of person they are, as well as ones that do not.
People that use Slackware, or Arch or such types as these too give themselves away as to what type of person they are.
Slackware can be a bleeding edge distribution quite eaiser then say Debian, or others that only do major releases of their distribution. By setting Slackware sources.list to pull off the current directory that keeps what they maintain current.
Then by the way Patrick Volkerding designed his distribution the owner/user still can keep everything he or she has installed on it "bleeding edge". Patrick Volkerding distribution gives the owner/user full access and ability to have to rely on his or hers ownself to ensure that they are the ones that have to deal with the majority of stress that comes with being independent and not codependent on someone else to do most if not all of the work and responsibility of ensuring everything that is installed on thier own system is "safe" and reliable, along with what the application too depends on to work is also safe and reliable to use so it can do what it was written to do.
With the use Slackbuilds only needing basic knowleadge of Bash scripting, and having to resolve dependencies that the software has allows this independency to the owner/user of Patrick Volkerding distribution of GNU/Linux. By the use of Slackbuilds one can eaisly install other software not kept current as the poster of this said that I am responding to, within Slackwares own standard release, and not in the current section of Slackwares repositories.
The system that he developed to keep track of everything can then be used to eaisly upgrade patch even remove said software in question. Because of the methodology that Patrick Volkerding uses to maintain his version of GNU/Linux allows the owner/user of his Operating System to learn and hone as well as use the ability to transpose knowleadge of how to get one item to perform operations using its inherited capabilities onto a different item to get it to perform operations using its own inherited capabilities using the same like methods.
As well as the opportunity to better learn how to deal with stress that comes along with the individuals choice to not only exersize his or hers own independence. Therefore, keeping themselves abay from becomming codependent but still giving the same owner/user of Slackware the ablitly to have a bleeding edge GNU/Linux Operating System that they have full say in everything that is bleeding edge on their system.
Finally, they that do can then take due credit for it. Therefore, they can take self pride with what they are doing this too helps raise low self esteem because they did it theselves. They did not fully relying on others to keep their needs of instant gradifcation satified by having to always have the lastest and greatest at all times so they can feel good about themselves because they give themselves something they can brag about that in thier minds makes them a better person then the other guy. even on a subconscious level therefore it is not even completely aparent to said person.
Actually, them that always need to be instantly gradified in one manner or another has a personality disorder. So to summerize, one that has a trained eye can tell what type of person the other is by what they do and say in life, and one of them things are the distro they pick to use.
Slackware can be an independent bleeding edge distro because Patrick Volkerding allows others there independence to keep it bleeding edge, not like the others that the users can or may become codependent as a result of it.
lol
