I just want to make sure if we (flightgear) have some outdated documentation
that gets identified and fixed. If someone managed to dredge up some really
old information from some other site, there's not much we can do about that.
Curt.
On Fri, Sep 11, 2009 at 11:21 AM, leee wrote:
> Although getting osg from cvs rang a bell with me, I'm not sure if
> those commands were ever on one of the FG sites: they relate back
> to when OSG was still hosted on sourceforge, as the link below
> shows...
>
> http://sourceforge.net/projects/openscenegraph/develop
>
> However, OSG moved from sourceforge to its own site in 2003. OSG
> was first discussed here during early August 2003, but I'm not sure
> if that was before or after OSG had moved from sourceforge to
> openscenegraph.org.
>
> In any case, Mathias Fröhlich didn't announce his work in porting it
> until late October 2006, so it's difficult to imagine why there
> would have been instructions on the FG sites for getting the 2003
> sourceforge osg vintage when it would have already been hosted at
> openscenegraph.org for more than three years.
>
> I should apologise for suggesting that FG was providing faulty
> instructions, but I still think that the 'note' was unnecessary as
> all it achieved was to aggressively suggest that the poster was
> lazy or stupid.
>
> Sure, people can be lazy _and_ stupid, but I can't see that
> attacking them for being so is the best way to do anything about
> it.
>
> LeeE
>
>
> On Friday 11 Sep 2009, Curtis Olson wrote:
> > Where are the misleading instructions located?
> >
> > Thanks,
> >
> > Curt.
> >
> > On Fri, Sep 11, 2009 at 7:39 AM, leee wrote:
> > > On Thursday 10 Sep 2009, Csaba Halász wrote:
> > > > On Thu, Sep 10, 2009 at 6:13 PM, Randall Green
> > >
> > > <randall.gr...@wright.edu> wrote:
> > > > > These are the instructions for checking out CVS OSG that
> > > > > are given:
> > > > >
> > > > > cvs
> > > > > -d:pserver:anonym...@openscenegraph.cvs.sourceforge.net:/cv
> > > > >sroo t/openscenegraph login
> > > > >
> > > > > cvs -z3
> > > > > -d:pserver:anonym...@openscenegraph.cvs.sourceforge.net:/cv
> > > > >sroo t/openscenegraph co -P modulename
> > > > >
> > > > > What is the modulename? I tried different things but
> > > > > nothing works.
> > > >
> > > > OSG has moved to SVN. Use this command:
> > > > svn co
> > > > http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk
> > > > OpenSceneGraph
> > > >
> > > > Note: it would have taken just a minute to go to the OSG web
> > > > site and find this information for yourself.
> > >
> > > I think your 'note' is a little unfair: we should not provide
> > > instructions that don't work and then tell people who try to
> > > follow those instructions that they should have figured out the
> > > correct instructions for themselves.
> > >
> > > LeeE
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel