Re: [cclib-devel] Molpro

[Noel O'B. <bao...@gm...>]

I would now modify my earlier quote slightly...if you are working on a
new parser just create a new branch of the trunk and start hacking -
don't worry about removing the bridges, and other modules, which is
what I suggest below.

On 29/01/07, Karol Langner <kar...@kn...> wrote:
> On Monday 29 of January 2007 23:14, you wrote:
> > Hi Karol,
> >
> > Noel and I decided it made sense to move Molpro (and any new parsers)
> > to their own branch for development until they are stable and ready
> > for inclusion in a release. We discussed it on a previous thread
> > awhile back, but under a different name. Here is the relevant text
> > from Noel:
> >
> > "...I was suggesting that development for new parsers should be done
> > on a branch, e.g. the molpro parser branch. This would only have
> > tests and data files for
> > molpro, for instance, and wouldn't contain the bridges, methods, etc.
> > modules, so that development would be more focused (and the only
> > changes would be parser related). Since Jaguar is slated for
> > inclusion in the next release, I think it'd be easier at this stage
> > to leave it on the trunk and do the final development there."
>
> OK - I'll dig into the archives when needed.
>
> > Out of curiosity, what parser are you thinking of adding?
> >
> > Adam
>
> I was thinking about Molcas. Maybe also mpqc when I have more time, for fun.
>
> Karol
>
> --
> written by Karol Langner
> Mon Jan 29 23:39:46 CET 2007
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> cclib-devel mailing list
> ccl...@li...
> https://lists.sourceforge.net/lists/listinfo/cclib-devel
>