Re: version/revision control software for things mostly not source
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/04/2010 18:08:14, Chad Perrin wrote: On Sat, Apr 17, 2010 at 06:37:10PM +0100, Matthew Seaman wrote: I'd recommend subversion for this -- configure it using HTTPS and with Apache's basic auth for access control. Use ViewVC for exploting your repos via the web -- if you take care to set appopriate MIME types as properties, then your browser should open files in the appropriate applications automatically. [Verb. Sap. ViewVC looks pretty ugly in the default view, but set template_dir=templates-contrib/viewsvn/templates in viewvc.conf for a much better result] Actually, on FreeBSD, I think it's a lot easier to get things going just using the command line client -- and you can explore the local copy of the repository using tools on the local machine just fine. I don't think a bunch of extra tools like a Webserver are necessarily the best option for a single user. Your mileage may vary, of course. Heh. I've spent so much time setting up apache configs that it's second nature to me. svnserve is certainly easier to get going in a basic setup, but tends to become rapidly more complex if you want to do anything much beyond that. Particularly if you want to offer read-only or anonymous access to your SVN repo -- doing that via apache is a lot easier, and probably a lot safer. Subversion is a big and complex beast, but the documentation is excellent. There's a whole book you can download here: It isn't terribly complex to set up using just the command line interface, though, if that's an acceptable interface for the user in question. Once the user gets used to it, it's quite simple to use, too. If all the bells and whistles you suggested are desired, though, it does get to be a bit more to manage. I find that all the effort is in the initial setup -- once it is up and running, it's pretty sweet and simple from the user point of view. For access from Windows, try TortoiseSVN. Luckily, TortoiseSVN is pretty easy to set up and use on MS Windows. Also, if you have a Mac, you can mount a SVN repo as a WebDAV fileshare. That's really quite nifty. The same thing should be possible from Windows, but there are some nasty bugs which get in the way. Rumour has it that explicitly adding a port number to the WebDAV URL makes things happier, but I've never tried that myself. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvKviUACgkQ8Mjk52CukIxETQCeIa+00eIx4uYr19lSo46c5Gec wjwAn1xqbTMNDbd4uAvfpFOspWAISjGo =DIT3 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: version/revision control software for things mostly not source
On Sun, Apr 18, 2010 at 4:10 AM, Gene f...@brightstar.bomgardner.net wrote: On Sat, 17 Apr 2010 18:08:49 +0300, Dan Naumov wrote I think I am reaching the point where I want to have some kind of sane and easy to use version/revision control software for my various personal files and small projects. We are talking about varied kind of data, ranging from binary format game data (I have been doing FPS level design as a hobby for over a decade) to .doc office documents to ASCI text formatted game data. Most of the data is not plaintext. So far I have been using a hacked together mix of things, mostly a combination of essentially storing each revision of any given file a separate file001, file002, file003, etc which while easy to use and understand, seems rather space-inefficient and a little bit of ZFS snapshotting, however I want something better. Sadly, FreeBSD's ZFS doesn't have dedup or this functionality would've been easy to implement with my current hacked together methods. Performance does't matter all that much (unless we are talking something silly like a really crazy IO bottleneck), since the only expected user is just me and perhaps a few friends. Thanks! - Sincerely, Dan Naumov Someone else mentioned Subversion and Tortoisesvn. I use these tools for revision management of 600 or so powerpoints, graphics, and other miscellaneous files that we use for church services. Once up and running, it's simplicity itself. I also use websvn to allow read only access to individual files via a browser. I've found it works like a charm. --- IHN, Gene I've looked at SVN and it looks reasonably easy to grok, but reading the Version Control with Subversion book... it seems there is no actual way to truly erase/delete/destoy/purge a part of an existing repository? This sounds rather weird and annoying. What if I decide that project XYZ is beyond redemption and abandon it, I delete the working copy of it, but all history is still in there, gigabytes upon gigabytes of data. With no way to remove it, it sounds like a really big limitation. - Sincerely, Dan Naumov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: version/revision control software for things mostly not source
Hello, On Sun, Apr 18, 2010 at 11:34 PM, Dan Naumov dan.nau...@gmail.com wrote: I've looked at SVN and it looks reasonably easy to grok, but reading the Version Control with Subversion book... it seems there is no actual way to truly erase/delete/destoy/purge a part of an existing repository? This sounds rather weird and annoying. What if I decide that project XYZ is beyond redemption and abandon it, I delete the working copy of it, but all history is still in there, gigabytes upon gigabytes of data. With no way to remove it, it sounds like a really big limitation. You can filter data out of a repository using svnadmin dump command. Regards Rambius -- Tangra Mega Rock: http://www.radiotangra.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: version/revision control software for things mostly not source
On Sun, 18 Apr 2010 23:34:19 +0300, Dan Naumov dan.nau...@gmail.com wrote: I've looked at SVN and it looks reasonably easy to grok, but reading the Version Control with Subversion book... it seems there is no actual way to truly erase/delete/destoy/purge a part of an existing repository? This sounds rather weird and annoying. What if I decide that project XYZ is beyond redemption and abandon it, I delete the working copy of it, but all history is still in there, gigabytes upon gigabytes of data. With no way to remove it, it sounds like a really big limitation. svndumpfilter may help. It also helps if you give each project it's own repository, but then the administration costs of setting up all the separate repositories are going to be non-negligible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: version/revision control software for things mostly not source
On Sun, Apr 18, 2010 at 11:34:19PM +0300, Dan Naumov wrote: I've looked at SVN and it looks reasonably easy to grok, but reading the Version Control with Subversion book... it seems there is no actual way to truly erase/delete/destoy/purge a part of an existing repository? This sounds rather weird and annoying. What if I decide that project XYZ is beyond redemption and abandon it, I delete the working copy of it, but all history is still in there, gigabytes upon gigabytes of data. With no way to remove it, it sounds like a really big limitation. The idea is that a VCS maintains a record of past revisions of the files in version control. Thus, even if you delete/destroy an entire subproject, it can later be recovered if necessary. VCSes are designed with the idea that each project gets its own version control repository. If you want to delete a project, then, you delete the repo for that particular project, and free up any space. If you maintain a huge filesystem containing lots of separate projects, on the other hand, you're essentially treating all of that filesystem as part of the same super-project, from the point of view of the VCS. Thus, there's nothing odd about the difficulty of clearing out part of what's stored in the repository. In fact, for purposes of recovering things you suddenly realize you shouldn't have deleted, this is a feature rather than a bug. As others have already noted, though, there are work-arounds that allow you to effectively delete something not just from the current working version, but from the whole repo. I won't repeat them here. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpM98E8PXT0D.pgp Description: PGP signature
Re: version/revision control software for things mostly not source
There's also a fuse-svnfs port for NetBSD, but I don't know its status, nor if it is usable at all: http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/filesystems/fuse-svnfs/ http://svn.haxx.se/users/archive-2005-04/0210.shtml -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
version/revision control software for things mostly not source
I think I am reaching the point where I want to have some kind of sane and easy to use version/revision control software for my various personal files and small projects. We are talking about varied kind of data, ranging from binary format game data (I have been doing FPS level design as a hobby for over a decade) to .doc office documents to ASCI text formatted game data. Most of the data is not plaintext. So far I have been using a hacked together mix of things, mostly a combination of essentially storing each revision of any given file a separate file001, file002, file003, etc which while easy to use and understand, seems rather space-inefficient and a little bit of ZFS snapshotting, however I want something better. What would be examples of good version control software for me? The major things I want are: a simple and easy to use Windows GUI client for my workstation, so I can quickly browse through different projects, go back to any given point in time and view/checkout the data of that point to a Windows machine. Space efficiency, while not critical (the server has 2 x 2TB drives in RAID1 and can easily be expanded down the line should the need eventually arise) is obviously an important thing to have, surely even with binary data some space can be saved if you have 20 versions of the same file with minor changes. Sadly, FreeBSD's ZFS doesn't have dedup or this functionality would've been easy to implement with my current hacked together methods. Performance does't matter all that much (unless we are talking something silly like a really crazy IO bottleneck), since the only expected user is just me and perhaps a few friends. Thanks! - Sincerely, Dan Naumov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: version/revision control software for things mostly not source
On Sat, Apr 17, 2010 at 5:08 PM, Dan Naumov dan.nau...@gmail.com wrote: I think I am reaching the point where I want to have some kind of sane and easy to use version/revision control software for my various personal files and small projects. You're looking for a versioning file system? http://en.wikipedia.org/wiki/Versioning_file_system -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: version/revision control software for things mostly not source
On Sat, Apr 17, 2010 at 06:08:49PM +0300, Dan Naumov wrote: I think I am reaching the point where I want to have some kind of sane and easy to use version/revision control software for my various personal files and small projects. We are talking about varied kind of data, ranging from binary format game data (I have been doing FPS level design as a hobby for over a decade) to .doc office documents to ASCI text formatted game data. Most of the data is not plaintext. snip What would be examples of good version control software for me? The major things I want are: a simple and easy to use Windows GUI client for my workstation, so I can quickly browse through different projects, go back to any given point in time and view/checkout the data of that point to a Windows machine. For text files, things like rcs work fine. But if you are handling binary files, you need something else. Personally, I like git. [http://git-scm.com/] Since I'm not a windows user, I cannot vouch for the windows client, but you can find some info at the follwing link. [http://nathanj.github.com/gitguide/tour.html] Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpGjFapoawvQ.pgp Description: PGP signature
Re: version/revision control software for things mostly not source
On Sat, Apr 17, 2010 at 06:08:49PM +0300, Dan Naumov wrote: I think I am reaching the point where I want to have some kind of sane and easy to use version/revision control software for my various personal files and small projects. We are talking about varied kind of data, ranging from binary format game data (I have been doing FPS level design as a hobby for over a decade) to .doc office documents to ASCI text formatted game data. Most of the data is not plaintext. So far I have been using a hacked together mix of things, mostly a combination of essentially storing each revision of any given file a separate file001, file002, file003, etc which while easy to use and understand, seems rather space-inefficient and a little bit of ZFS snapshotting, however I want something better. What would be examples of good version control software for me? The major things I want are: a simple and easy to use Windows GUI client for my workstation, so I can quickly browse through different projects, go back to any given point in time and view/checkout the data of that point to a Windows machine. Space efficiency, while not critical (the server has 2 x 2TB drives in RAID1 and can easily be expanded down the line should the need eventually arise) is obviously an important thing to have, surely even with binary data some space can be saved if you have 20 versions of the same file with minor changes. Sadly, FreeBSD's ZFS doesn't have dedup or this functionality would've been easy to implement with my current hacked together methods. Performance does't matter all that much (unless we are talking something silly like a really crazy IO bottleneck), since the only expected user is just me and perhaps a few friends. If you're looking for local revision management, I think something like Mercurial is an excellent choice. If, however, you're looking more for a system for backing up to a remote computer with revision management included in the package, Subversion may be a better choice. This is because the basic assumption for distributed version control systems like Mercurial (which I love) is that you'll be working on stuff locally and want the ability to move forward and backward through changes, run parallel development branches locally to try out things and compare your results and so on, with occasional reintegration with others' efforts. By contrast, a centralized VCS like Subversion operates on the basic assumption that all your work is intended to be stored on some centralized system, and when you want to commit a particular revision you also want it at that moment to be backed up to that central location. I think this is why Subversion was fairly popular as a simple, manual backup system for a lot of people, while DVCSes like Mercurial tend to be popular more specifically with software developers -- particularly in open source projects. So . . . depending on your particular needs and workflow, I'd say that a centralized VCS and a DVCS are both candidates for best option in your case. Note: I use Subversion and Mercurial as my examples because those are the two I generally use and like the most. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpADYbPfUiOO.pgp Description: PGP signature
Re: version/revision control software for things mostly not source
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/04/2010 16:08:49, Dan Naumov wrote: I think I am reaching the point where I want to have some kind of sane and easy to use version/revision control software for my various personal files and small projects. We are talking about varied kind of data, ranging from binary format game data (I have been doing FPS level design as a hobby for over a decade) to .doc office documents to ASCI text formatted game data. Most of the data is not plaintext. So far I have been using a hacked together mix of things, mostly a combination of essentially storing each revision of any given file a separate file001, file002, file003, etc which while easy to use and understand, seems rather space-inefficient and a little bit of ZFS snapshotting, however I want something better. What would be examples of good version control software for me? The major things I want are: a simple and easy to use Windows GUI client for my workstation, so I can quickly browse through different projects, go back to any given point in time and view/checkout the data of that point to a Windows machine. Space efficiency, while not critical (the server has 2 x 2TB drives in RAID1 and can easily be expanded down the line should the need eventually arise) is obviously an important thing to have, surely even with binary data some space can be saved if you have 20 versions of the same file with minor changes. Sadly, FreeBSD's ZFS doesn't have dedup or this functionality would've been easy to implement with my current hacked together methods. Performance does't matter all that much (unless we are talking something silly like a really crazy IO bottleneck), since the only expected user is just me and perhaps a few friends. I'd recommend subversion for this -- configure it using HTTPS and with Apache's basic auth for access control. Use ViewVC for exploting your repos via the web -- if you take care to set appopriate MIME types as properties, then your browser should open files in the appropriate applications automatically. [Verb. Sap. ViewVC looks pretty ugly in the default view, but set template_dir=templates-contrib/viewsvn/templates in viewvc.conf for a much better result] Subversion is a big and complex beast, but the documentation is excellent. There's a whole book you can download here: http://svnbook.red-bean.com/nightly/en/svn-book.pdf For access from Windows, try TortoiseSVN. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvJ8cYACgkQ8Mjk52CukIw1sgCdGZhmhRs+MpPeL+ySuROihznh dgIAn0KU7pf88IQkxrx3aZLKc2ABDi1x =yxTX -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: version/revision control software for things mostly not source
On Sat, Apr 17, 2010 at 06:37:10PM +0100, Matthew Seaman wrote: I'd recommend subversion for this -- configure it using HTTPS and with Apache's basic auth for access control. Use ViewVC for exploting your repos via the web -- if you take care to set appopriate MIME types as properties, then your browser should open files in the appropriate applications automatically. [Verb. Sap. ViewVC looks pretty ugly in the default view, but set template_dir=templates-contrib/viewsvn/templates in viewvc.conf for a much better result] Actually, on FreeBSD, I think it's a lot easier to get things going just using the command line client -- and you can explore the local copy of the repository using tools on the local machine just fine. I don't think a bunch of extra tools like a Webserver are necessarily the best option for a single user. Your mileage may vary, of course. Subversion is a big and complex beast, but the documentation is excellent. There's a whole book you can download here: It isn't terribly complex to set up using just the command line interface, though, if that's an acceptable interface for the user in question. Once the user gets used to it, it's quite simple to use, too. If all the bells and whistles you suggested are desired, though, it does get to be a bit more to manage. For access from Windows, try TortoiseSVN. Luckily, TortoiseSVN is pretty easy to set up and use on MS Windows. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpSi5VKpKnWv.pgp Description: PGP signature
Re: version/revision control software for things mostly not source
I should have mentioned this in my previous email: If you don't think you actually need a full-blown VCS, you can get a certain amount of roll-back capability out of rsync too. To ensure you get the best tools for the job, it pays to compare your actual needs with the capabilities of the tools you have available to you. I suspect, from what little information has been offered so far, that Subversion will probably be the most suitable tool -- but there's a certain amount of guesswork in that, and only the person who needs to select the tool can be sure what best suits his needs. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpuzvfFOMQcx.pgp Description: PGP signature
Re: version/revision control software for things mostly not source
On Sat, 17 Apr 2010 18:08:49 +0300, Dan Naumov wrote I think I am reaching the point where I want to have some kind of sane and easy to use version/revision control software for my various personal files and small projects. We are talking about varied kind of data, ranging from binary format game data (I have been doing FPS level design as a hobby for over a decade) to .doc office documents to ASCI text formatted game data. Most of the data is not plaintext. So far I have been using a hacked together mix of things, mostly a combination of essentially storing each revision of any given file a separate file001, file002, file003, etc which while easy to use and understand, seems rather space-inefficient and a little bit of ZFS snapshotting, however I want something better. Sadly, FreeBSD's ZFS doesn't have dedup or this functionality would've been easy to implement with my current hacked together methods. Performance does't matter all that much (unless we are talking something silly like a really crazy IO bottleneck), since the only expected user is just me and perhaps a few friends. Thanks! - Sincerely, Dan Naumov Someone else mentioned Subversion and Tortoisesvn. I use these tools for revision management of 600 or so powerpoints, graphics, and other miscellaneous files that we use for church services. Once up and running, it's simplicity itself. I also use websvn to allow read only access to individual files via a browser. I've found it works like a charm. --- IHN, Gene -- To everything there is a season, And a time to every purpose under heaven. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
