On Friday, July 17, 2015 09:17:58 AM Kevin Squire wrote:
> It might be a good idea for HDF.jl to load and provide JLD.jl for a short
> deprecation period.
How would this work precisely? Put something in the build script like
if !Pkg.installed("JLD")
warn("Adding the JLD package, which has been split off from HDF5")
Pkg.add("JLD")
end
Might indeed solve some problems, but I'm worried it could cause some
annoyance, too. I'm actually not 100% sure this would work, since JLD depends
on HDF5...
If this is workable, for how many versions of HDF5 should we keep this
feature? If folks don't update for a month and we've already dropped it,
they'll miss it.
--Tim
>
> On Friday, July 17, 2015, Matt Bauman <[email protected]> wrote:
> > How should packages that depend upon JLD update their REQUIRE files?
> > Should they just tag a new version that requires JLD instead (or in
> > addition to, if they also use HDF5's capabilities)?
> >
> > On Friday, July 17, 2015 at 10:14:27 AM UTC-4, Tim Holy wrote:
> >> Hi folks,
> >>
> >> If you use HDF5/JLD, the next time you update packages you probably want
> >> to
> >> say Pkg.add("JLD"). JLD has been split off from HDF5 into a separate
> >> package,
> >> so when HDF5 updates you will lose JLD functionality unless you add the
> >> new
> >> package.
> >>
> >> Going forward, you only need to say "using JLD" rather than "using HDF5,
> >> JLD."
> >> That said, there's no harm in the latter, and you'll need it anyway if
> >> you're
> >> in the habit of using HDF5 functionality like creating groups, etc.
> >>
> >> Best,
> >> --Tim
