| How to create a stable "package" in IDL? [message #85322] |
Wed, 24 July 2013 10:33  |
![Paul Van Delst[1] is currently offline](theme/default/images/xoffline.png.pagespeed.ic.XRkd1fkXye.png "Paul Van Delst[1] is currently offline")
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
Hello,
I have a bunch of IDL software used to process satellite data. Works great.
The problem is I'm a tinkerer. I'm always trying to either "improve"
algorithms or make them run a bit faster. And that leads to slight
differences in the results - which is generally o.k. for me as I can
identify where/how the differences originated, but for other users that
checkout our IDL codebase it can be a bit frustrating.
What I want to do is create a release of a *subset* of IDL software
within our IDL repository. The problem I have is how to do that within
the IDL directory structure. I can't guarantee that other users will
have their IDL_PATH variable set such that they will get to the stable
release directory first, as opposed to the still-in-development directory.
Does anyone with experience in both IDL and version control have a
solution for this? I have to admit I'm experiencing a case of brainfade
about it.
I thought of the compiled-language approach (i.e. build a library from a
checked out tag and install in a default location), but then how would a
developer switch between the stable and development codes without
mucking about with IDL_PATH? (Which I would forget at some point)
Hopefully my question makes sense. Thanks for any info.
cheers,
paulv
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
