| 9:53 am on Oct 2, 2011 (gmt 0)|
SourceSafe for Unix?:
| 2:50 pm on Oct 20, 2011 (gmt 0)|
Thank you phranque, I'm a bit stuck...I'm going through all the readme files and the like however I'm not sure how to install this on Linux. I'm running a copy of Debian. I'm not familiar with Linux install paths (there are 23 folders in the root!). I'm guessing I simply copy and paste? How does Linux know that the files are there?
| 3:06 pm on Oct 20, 2011 (gmt 0)|
Actually I found them however I'm confused...
|Copy "ss" to prefix/bin (where prefix is usually /usr/local), and *.pm files in prefix/lib/ss (/usr/local/lib/ss/Maps.pm etc). "ss" should be executable. |
So my best interpretation is that there are files that start with the letters 'ss' (but not files with that extension) and I tried to copy them to 'usr/local/bin' however it denies me the permission to do that, not that I think this is solidly what the directions say the above is written as clearly as a completely frosted over windshield.
I also don't have permission to create a folder in '/usr/local/lib/'.
| 4:05 pm on Oct 20, 2011 (gmt 0)|
Figured it out, nautilus-gksu (can be found in the package manager) adds a context menu so you can right-click on a folder and open it with root permissions. It should be that way by default.
I copied the ss files to...
~/usr/local/ss (as file, not folder)
...and the pm files to...
~/usr/local/lib/ss/Maps.pm (as example with /ss/ being a folder)
I *think* this is what was intended.
I'm really lost on this part which I think is intended for SSH however I'm running Debian locally in VirtualBox...
|For each user create ~/.ssrc (mode 600), containing: |
Where HOME is an absolute path to an existing directory that will contain your SourceSafe projects, and MAP is an association list of directories to databases (see the MAP configuration reference).
In the above example we assume that ss will have control of all the /home/username/projects tree, and the directory /home/username/projects/dirname will actually contain the db/projectname project (where you recall DB was configured server-side as C:\\DATA\\SSAFE_DB, yielding C:\DATA\SSAFE_DB $/projectname in SourceSafe syntax).
Execute ss get to bootstrap your tree.
Those directions are referencing paths that SS will reference, the problem is I'm not sure where to put the file .ssrc itself! Does "~/.ssrc" mean the very root of the entire hard drive? Of the user folder? Or ~/home/john/.ssrc?
| 6:00 am on Oct 24, 2011 (gmt 0)|
the tilde (~) in th file path is a shorthand/symbol for the user's home directory, so it looks like /home/john/.ssrc is the file location in your case.
| 9:55 pm on Oct 29, 2011 (gmt 0)|
Thank you, I'm not used to the paths in Linux and there are a lot of them.
I just want to post what I have thus far to keep the thread from getting to old to follow-up. Here are the directions I've been able to confirm thus far (not finished getting this to work yet however) here to help others out should they have difficulty with the instructions like I did...
Using Debian with the default file manager Nautilus I confirmed the file locations and was able to gain permission to copy them using nautilus-gksu (can be found in the package manager)...
The ss files are copied to...
/usr/local/ss (as file, not folder)
The *.pm files are copied to...
/usr/local/lib/ss/Maps.pm (as example with /ss/ being a folder)
I've confirmed that much. I was able to show hidden files (under the view menu) and create the file .ssrc.
Using the directions in ssu-0.10/README.html#ss-client I'm a bit stuck though (ssu is still an unknown command and I'm not sure what the server path should be and if I should HAVE a server path for this; also confused since there is no "ssu" file anywhere) and have limited time to make this post. I'll be following it up in a few days though. Thank you for your help phranque. :)
| 11:45 am on Oct 31, 2011 (gmt 0)|
ssu may be an alias. Unix allows you to abbreviate commands as well as set common defaults for commands using the alias command.
| 9:53 pm on Oct 31, 2011 (gmt 0)|
try using the whereis or similar command:
i'm not sure this will work in your case since ssu appears to be "unknown" but perhaps you might get a clue from this.