Code: Select all
spkg -u chromium-<new-version>.txz
Code: Select all
spkg -u chromium-<new-version>.txz
Code: Select all
sudo <some command needing root privileges>
Code: Select all
sudo su
In this repository chromium was present..slackonly wrote:Hi!
I just start a project to make all slackbuilds in packages in a repository (later i will add and dependencies support!)
If you have time just look my site http://slackonly.com/pub/packages/14.1-x86_64/
At the current time i have finish desktop and multimedia section.
My aim is at the same time simultaneously making and dependencies for the packages and testing to my pc to make sure all working good.
Any comments or suggestion is highly appreciated...
Thanks...
Will keep that in mind.mimosa wrote:It is not advised to mess with the included repsotories in Gslapt, unless you really know what you are doing; and if you are inclined to do that, you probably don't. The whole point of a distribution's repositories is they come tested and guaranteed. Some distros may not be too careful about that, but so much the worse for them.
It is certainly not a good approach to getting an individual package you can't find in the repos. In that case, much better to download and manually install one particular package whose provenance you have reason to be confident about.
Adding a whole other repository is very likely to break your system, because those packages haven't been built and tested against the other ones in the Salix repositories.
EDIT
In this case, looking at that link, someone claims to be in the process of doing so for a number of packages (as a Work In Progress, with dependencies to come in the future). But this is a project from outside the Salix team, without the quality assurance and procedures intended to guarantee the consistent standard of Salix packages. Such an outside repoisitory may prove its worth as a source of extra packages for judicious one-off manual instsallation; but to incorporate it within an installed Salix system's package management would mean watering down the latter and, almost certainly, introducing errors in dependency handling, even if not in actual packages. This would lead to problems beyond the ability of an inexperienced user to handle, aka a broken system. On the other hand, an experienced user should have no trouble building the packages from source, and dealing with all the same depe3ndency issues.