#1137162 simint: sources should contain the generator, not the generated files

#1137162#5
Date:
2026-05-20 07:29:35 UTC
From:
To:
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.

#1137162#10
Date:
2026-06-18 15:45:40 UTC
From:
To:
I guess you refer to this:

https://github.com/simint-chem/simint-generator

How do people handle this kind of issues in practice?

Would converting the package into a multi-tarball package work?

Thanks.

#1137162#15
Date:
2026-06-18 15:51:20 UTC
From:
To:
Yes.

Is there anything in the generated files that is not in the generator?

(Not a rhetorical question, I did not double-checked that.)

cu
Adrian

#1137162#20
Date:
2026-06-18 16:11:25 UTC
From:
To:
No idea, but I hope Michael can answer that at some point.

I've just fixed the baseline violation because it looked feasible
without spending too much time. Merging two different source packages
into one looks a lot more troublesome.

Thanks.

#1137162#25
Date:
2026-06-19 09:22:30 UTC
From:
To:
Hi,

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...

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

Thanks for that.

Yeah.


Michael