Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
If you create a "PUBLIC" branch from HEAD (where you have the open code), then set permissions on trunk and branch such that the anonymous users are only able to check out the branch whereas your developers can check out everything then it might work. But I have never used the acls on branches myself so I cannot say for sure what will happen... Someone else?? /Bo -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of Koen Sent: den 20 januari 2005 14:52 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Letting some users only see versions older than date X ? Hi, I think this is going to be a hard one, but you never know with you guys ;-) Is it possible somehow to let some cvs users only read/checkout files from the repository that were committed AFTER a certain date? Background: We have some software that was previously released as closed-source (v. 1.00). Then a year and some modifications later, I set up a CVS repository to manage that code (fed up with mailing zip files back and forth and all the related issues with that...) Then, now that the project is finished, the source code is going to be released under a GNU GPL license (v. 1.01). Therefore, a GPL notice was added in each file. I would now like the world to have read-only access to this repository. For the latest committed files, I have -as said- added the GPL notice in the files, but of course, if people have read access to the repository, they can check out previous versions of the software that do not contain that notice. And that's what I would like to prevent. I had thought about seting up a new repository and importing the latest code from the previous repository as a starting point, so that there will be no "not-GPL'ed" files to check out. But of course, this way, I will loose my complete history of the repository... Hence my thought of keeping what I have, but restricting checkout and update for a public cvs user. Pfeww... Hope this is clear... Koen _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs