How to?
- Tim CowChip
- Posts: 304
- Joined: 27. May 2011, 03:35
- Location: Cascade Locks, OR
Re: How to?
Code: Select all
spi --search pulseaudio
spi --search gedit
You will increase the search area by adding "SOURCE=http://slackbuilds.org/slackbuilds/14.1/" to /etc/slapt-get/slapt-srcrc
Re: How to?
spi already looks at slackbuilds where there is no such package in Slackware / Salix repositories. That is the whole point of it. Check out the package management section in the Salix Startup Guide:
http://guide.salixos.org/321SalixPackag ... html#4_2_1
In general, it is not a good idea to change slapt-getrc or slapt-srcrc unless you really know what you are doing.
EDIT
Returning to the original question, if you prefer a graphical interface to package management, just search for what you're looking for with Gslapt. Make sure you do 'Update' first to download the latest package lists. If you don't find it there, try Sourcery, which searches for Slackbuilds. All this is described in more detail in the Guide.
http://guide.salixos.org/321SalixPackag ... html#4_2_1
In general, it is not a good idea to change slapt-getrc or slapt-srcrc unless you really know what you are doing.
EDIT
Returning to the original question, if you prefer a graphical interface to package management, just search for what you're looking for with Gslapt. Make sure you do 'Update' first to download the latest package lists. If you don't find it there, try Sourcery, which searches for Slackbuilds. All this is described in more detail in the Guide.
Re: How to?
This was true about a year or so ago when the salix repo just had a static copy of http://slackbuilds.org/slackbuilds/, but now http://salix.enialis.net/sbo/ is truly a mirror being synced to the slackbuild repo daily. So adding this line is now redundant.Tim CowChip wrote:You will increase the search area by adding "SOURCE=http://slackbuilds.org/slackbuilds/14.1/" to /etc/slapt-get/slapt-srcrc
“Don’t you see that the whole aim of Newspeak is to narrow the range of thought?"
- Tim CowChip
- Posts: 304
- Joined: 27. May 2011, 03:35
- Location: Cascade Locks, OR
Re: How to?
I tried replacing the http://slackbuilds.org/slackbuilds/14.1/ line with http://salix.enialis.net/sbo/14.1/laprjns wrote:This was true about a year or so ago when the salix repo just had a static copy of http://slackbuilds.org/slackbuilds/, but now http://salix.enialis.net/sbo/ is truly a mirror being synced to the slackbuild repo daily. So adding this line is now redundant.Tim CowChip wrote:You will increase the search area by adding "SOURCE=http://slackbuilds.org/slackbuilds/14.1/" to /etc/slapt-get/slapt-srcrc
and couldn't find conky-1.9 with sourcery.
I switched back to the http://slackbuilds.org/slackbuilds/14.1/ line and found it again.
Re: How to?
My apologies, although the repo is being updated daily, there is some logic to exclude slkbuilds of applications when packages for the application already exit in salix binary repo. So using the example of conky, the package, conky-1.9.0-x86_64-2dj exit in the salix binary repo so when the salix sbo mirror is rysnc'e the conky slackbuid in excluded from the salix sbo repo. So maybe adding the sbo repo line is not redundant, but it does bring in some complications if you install packages that conflict with the salix binary repo packages.laprjns wrote:Tim CowChip wrote:This was true about a year or so ago when the salix repo just had a static copy of http://slackbuilds.org/slackbuilds/, but now http://salix.enialis.net/sbo/ is truly a mirror being synced to the slackbuild repo daily. So adding this line is now redundant.
“Don’t you see that the whole aim of Newspeak is to narrow the range of thought?"