Hi,

> > > > The sources should contain the generator, not the generated files.
> > > > 
> > > > Passing "-l 7 -p 0" to create.py seems to be equivalent to the
> > > > generated files, and the result builds for me.
> > > 
> > > I guess you refer to this:
> > > 
> > > https://github.com/simint-chem/simint-generator
> > 
> > Yes.
> > 
> > > How do people handle this kind of issues in practice?
> > > 
> > > Would converting the package into a multi-tarball package work?

That sounds ugly, why not just replace the current source package with
the generator one? Either yank the simint source package completey and
package simint-generator instead, or we issue a 0.7ds.1 or so source
package with the generator.

Normally I'd say let's just wait for the next upstream release, but 0.7
was released in 2017, so...

> > Is there anything in the generated files that is not in the generator?
> > 
> > (Not a rhetorical question, I did not double-checked that.)
> 
> No idea, but I hope Michael can answer that at some point.

I don't know either, but I guess not.

> I've just fixed the baseline violation because it looked feasible
> without spending too much time. 

Thanks for that.

> Merging two different source packages into one looks a lot more
> troublesome.

Yeah.


Michael

Reply via email to