"Sean 'Shaleh' Perry" wrote:
> > I maintain the xtide package. Currently, it's not a pristine
> > package: I add harmonics data to the package that are otherwise
> > downloaded manually from the author's web site (it was packaged
> > this way when I adopted it). Since the xtide software itself
>
> I maintain the xtide package. Currently, it's not a pristine
> package: I add harmonics data to the package that are otherwise
> downloaded manually from the author's web site (it was packaged
> this way when I adopted it). Since the xtide software itself and
> the harmonics data are updated
[I sent this to -devel yesterday morning and got no replies.
Thought I'd try here. I'm pretty much decided to go with option
#1 below, but welcome advice.]
I'm seeking a bit of advice about an upcoming package split.
I maintain the xtide package. Currently, it's not a pristine
package: I add
"Sean 'Shaleh' Perry" wrote:
> > I maintain the xtide package. Currently, it's not a pristine
> > package: I add harmonics data to the package that are otherwise
> > downloaded manually from the author's web site (it was packaged
> > this way when I adopted it). Since the xtide software itself
>
> I maintain the xtide package. Currently, it's not a pristine
> package: I add harmonics data to the package that are otherwise
> downloaded manually from the author's web site (it was packaged
> this way when I adopted it). Since the xtide software itself and
> the harmonics data are update
[I sent this to -devel yesterday morning and got no replies.
Thought I'd try here. I'm pretty much decided to go with option
#1 below, but welcome advice.]
I'm seeking a bit of advice about an upcoming package split.
I maintain the xtide package. Currently, it's not a pristine
package: I ad
6 matches
Mail list logo