2012/2/29 Jeremy Bennett <[email protected]>: > On Wed, 2012-02-29 at 13:16 +0000, R. Diez wrote: >> Hi Jeremy: >> >> >> > The GNU tools are held at: >> > >> > http://opencores.org/ocsvn/openrisc/openrisc/trunk/gnu-src >> >> The gnu-src repository is huge and takes a long time to check out, >> especially under Cygwin. These are the some of the subdirectories: >> >> bd-elf >> bd-elf-gdb >> binutils-2.18.50 >> binutils-2.20.1 >> gcc-4.2.2 >> gcc-4.5.1 >> gdb-6.8 >> gdb-7.1 >> gdb-7.2 >> newlib-1.17.0 >> newlib-1.18.0 >> >> I don't see why the average developer should download both the old and the >> new versions of GDB, Newlib and GCC every time. Some key components, like >> the or1ksim, must be downloaded separately anyway. > > That is a good point. We should keep the legacy in a separate directory. > I'll look at reorganizing the SVN hierarchy to do this. > >> I would remind any new developer that the OpenCores Subversion >> repositories are behind a registration wall >> that wants some personal information from you, probably for marketing >> purposes. There is no anonymous access, so they have full control >> about who is allowed to look at the code inside. If anything happens >> to the foundation/company/whatever behind these servers, there are no >> public mirrors that I know of, so at least the check-in history would >> probably be lost. > > This is a long-standing issue with OpenCores, but does not affect > whether you use git or SVN. It is about whether you use OpenCores or > GitHub (or SorceForge for that matter). > >> By the way, Github can emulate a Subversion server, so users do not >> even need to learn git, and Subversion repositories can add external >> references to Github repos as if they were normal Subversion >> repositories, see here: >> >> https://github.com/blog/966-improved-subversion-client-support >> > > We are rather going down the route of "git is the answer, now how do we > change the question to fit the answer". I use SVN, CVS and git > professionally. They all have their strengths and weaknesses. For every > expert who marvels at the richness of git, there is a beginner baffled > by its complexity. The answer is to use the right tool for each job. > > And for the whippersnappers out there, I'd just like to point out that > we didn't have all these difficulties when there was just RCS. And don't > get me started on the simplicity of just using a quill pen. And another > thing, what's wrong with clay tablets for note taking... > > > Jeremy > > -- > Tel: +44 (1590) 610184 > Cell: +44 (7970) 676050 > SkypeID: jeremybennett > Email: [email protected] > Web: www.embecosm.com > > _______________________________________________ > OpenRISC mailing list > [email protected] > http://lists.openrisc.net/listinfo/openrisc
We have talked briefly about this before, and I agree that we should store away older versions as they get replaced by newer ones. One thing to note though, is that a lot of people seem to use older versions of some components. I have especially seen many people asking for help with gdb 6.8 -- Olof Kindgren ______________________________________________ ORSoC Website: www.orsoc.se Email: [email protected] ______________________________________________ FPGA, ASIC, DSP - embedded SoC design _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
