We haven't been all that strict about inter-package version dependencies so far. You could determine the minimum supported version of your dependency that you need with a series of Pkg.pin and Pkg.test steps if you aren't sure about the most recent feature or bugfix you need. Otherwise I think leaving off the version floor is okay at this stage, until any users report a problem.
On Wednesday, September 2, 2015 at 11:44:05 AM UTC-7, David Anthoff wrote: > > Hi all, > > > > couple of questions on best practices for package devs: > > > > 1) My package needs the Dates package on julia 0.3, but not on julia 0.4. > I assume I just have to leave Dates in the REQUIRE file if I want both > versions of julia supported, right? > > > > 2) Generally, how are people handling minimum versions of dependent > packages? Right now I just list all the packages that my package needs, > without any version qualification. But I’m sure my package doesn’t work > with a super old version of some of these packages. But figuring out what > the minimum package version of dependent packages is that works with my > package would be a LOT of work. I could of course just put the current > versions as the minimum versions in, but then I might cause trouble for > other packages that require an older version of one of these dependent > packages. How are others handling this whole issue? > > > > Thanks, > > David > > > > -- > > David Anthoff > > University of California, Berkeley > > > > http://www.david-anthoff.com > > >
