Hello Stoyan, Just 3 months behind, as the new holidays came to our land, I've found a free night to learn about svn. I didn't get cvs2svn working under OpenSolaris, so I imported the current source dir to the repository using "svn" only. Surprisingly, it just worked :)
Thus, my current development tree has at last moved to filibeto. I've also made a new release of Solaris packages using some updated files. See this all at https://svn.sun-rays.org:4443/FLButselector/trunk Happy International Women's day to all the girls on the list ;) Saturday, December 22, 2007, 3:47:24 PM, you wrote: SA> Jim Klimov wrote: >> Hello Stoyan, >> SA> hello Jim, >> I really appreciate your invitation, and the site devoted >> to Sun Rays does indeed seem to be the best place for such >> a project as mine, especially to get it widely available. >> Besides, I'll score being second in your SVN repository :) SA> you are welcome! if you want some content published on the web page SA> (sun-rays.org) just send me the html pages/pictures/packages etc. and SA> i'll put them on the web server. you can also create a pages and upload SA> files on the wiki using your registered user. >> It might be a prime time to settle on some name for the >> project [directory], too. There's a problem: I planned to >> split this into several Solaris packages (framework, sample >> application wrappers, neighboring scripts like utumountusb), >> so there should be some short basename to extend when making >> packages. Can you suggest anything appropriate? >> >> Would SUNWutselector be too long a base name (follows the >> GNOME long package names though)? And is it too bold with >> SUNW up front? :) >> SA> i think SUNWutselector is ok as base name and the extended name SA> SUNWutselector-<subname> will be nice as it will be more informative. SA> regarding the "SUNW" part i think it is ok to keep it as it is also used SA> for the remote control toolkit. SA> i personally use the FLB prefix (from "filibeto") when i create SA> packages, but this is just my personal choice ;) >> I have sent you an SVN Commit Request from the web form. SA> your "commit access" account is ready - the user and password are set as SA> per the "How to get commit access" section on the subversion page on the SA> wiki (http://wiki.sun-rays.org/index.php/Subversion). please let me know SA> if you experience any problems using the account. >> >> Is there a simple way to import a CVS project (at our site) >> to SVN (at your site)? Will $Id:$ tags break in the process? SA> you can try using the cvs2svn python script SA> (http://cvs2svn.tigris.org/). one of the features mentions "No SA> information lost" :) SA> if your CVS repository has multiple projects you can use the options SA> file method (http://cvs2svn.tigris.org/faq.html#onetoone)to export only SA> the SUNWutselector project. you also need to use the SA> "--dumpfile=<dumpfile>" output option to produce an svn dump file. SA> having the dump file i can try to importi it to the current repository. SA> if anyone else with more experience on this can suggest a better way to SA> do this - please post to this thread. >> Or should I simply commit my files and start the numbering >> from point zero? SA> it is up to you - if you think the CVS export will be too much of a SA> hassle... SA> note that subversion tends to use repository-global revision numbers, SA> and as i try to stick to the "single repository/multiple projects" model SA> you may note that the youngest revision number for the repository keeps SA> changing because of other project(s) adding revision. >> >> Thank you. >> SA> please let me know if i can help with anything else. SA> greetings, SA> Stoyan -- Best regards, Jim Klimov mailto:[EMAIL PROTECTED] _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
