Salix current
Posted: 16. Oct 2012, 16:12
For years I have been tracking Slackware current with KDE/Trinity 3. As Trinity 3.5.13 is showing some bitrot *) and I like Xfce I installed Salix 14.0 and changed the "14.0" in the slapt-get sources to "current" (as 14.0 and current are (almost) identical this can be done easily).
To my dismay however I noticed that the "current" repos were removed a day or two ago. Some googling showed that the Salix current repos are created around a Slackware RC1 time, and are removed again after the Slackware release.
But I want to track Slackware current ...
As I see things I have 3 options:
1) Use the Slackel repos - the "official" ones point to Slackware current and the "preferred" one to Salix 14.0. As I am not interested in KDE 4 I can leave out the "custom" repo.
2) Create my own Slackware current repos - with the docs and scripts this should not be that difficult.
3) Stay with Slackware current and manually track/download/install/update the Salix 14.0 packages. As the number of those packages is overseeable this should be a viable, though somewhat kludgy alternative.
Any comments would be appreciated.
Kind regards, Dick
*) In the meantime Trinity 3.5.13.1 is released - whether or not that version resolves the problems I do not know (yet).
To my dismay however I noticed that the "current" repos were removed a day or two ago. Some googling showed that the Salix current repos are created around a Slackware RC1 time, and are removed again after the Slackware release.
But I want to track Slackware current ...
As I see things I have 3 options:
1) Use the Slackel repos - the "official" ones point to Slackware current and the "preferred" one to Salix 14.0. As I am not interested in KDE 4 I can leave out the "custom" repo.
2) Create my own Slackware current repos - with the docs and scripts this should not be that difficult.
3) Stay with Slackware current and manually track/download/install/update the Salix 14.0 packages. As the number of those packages is overseeable this should be a viable, though somewhat kludgy alternative.
Any comments would be appreciated.
Kind regards, Dick
*) In the meantime Trinity 3.5.13.1 is released - whether or not that version resolves the problems I do not know (yet).