Re: [Rdkit-devel] updating the rdkit project on sourceforge
Open-Source Cheminformatics and Machine Learning
Brought to you by:
glandrum
|
From: Greg L. <gre...@gm...> - 2012-08-17 09:36:13
|
Here is, hopefully, the last update on this topic. Apologies for the verbosity. One unfortunate thing about this update is that the svn repository has moved. If you have a version of the source checked out via svn, you need to change the repository URL. You have a few choices: 1) checkout a fresh copy (instructions for how to do that are here: http://sourceforge.net/p/rdkit/code) 2) switch your existing copy. The method for the switch depends on how you checked out the code in the first place, but this is what I just did : svn switch --username glandrum --relocate https://rdkit.svn.sourceforge.net/svnroot/rdkit/trunk https://svn.code.sf.net/p/rdkit/code/trunk I'm not quite sure why, but this worked for me on linux, but not on the Mac. 3) If you have unchecked-in changes that you want to keep, you can do something like this: - cd $RDBASE - svn update - cd .. - svn diff $RDBASE > rdk.patch - mv $RDBASE $RDBASE.old - <do a fresh rdkit checkout as directed in option 1 above>, make sure it goes into the directory $RDBASE - patch -p0 < ./rdk.patch Best, -greg On Fri, Aug 17, 2012 at 8:25 AM, Greg Landrum <gre...@gm...> wrote: > Ok, the change I mentioned below has been made; we're now using the > new sourceforge tools. > > I've update the links on www.rdkit.org. > > The svn migration is still ongoing, so at the moment svn is unavailable. > Once the migration is complete, people who are using the RDKit svn > repository will need to change their local copies. > I'll send information about how to do this once the migration has finished. > > -greg > > > On Thu, Aug 16, 2012 at 5:24 AM, Greg Landrum <gre...@gm...> wrote: >> Dear all, >> >> Sourceforge has new backend software that they are encouraging >> everyone to switch their projects too. >> Based on the descriptions >> (https://sourceforge.net/p/allura/wiki/Features/) it sounds like a >> good idea to me, so I plan to go ahead and initiate the update in the >> next couple of days (unless one of you has a strong opinion that it >> would be a bad idea). >> >> Aside from a more modern web experience and the new features described >> above, the only real significant change that you should see is that >> the URLs for the svn repository will change. I will send updated info >> about this after the switch (when I know the new urls). >> >> For those interested, there are some details about the upgrade process >> here: https://sourceforge.net/p/upgrade/ >> >> Best, >> -greg |