Bug#833193: chapel/1.15 [ITP]
Hi Sean,
> Dear Ben,
>
> Thank you again for this well-organised response.
>
> To return the favour, in this e-mail I'll
>
> * discuss some logistics around this RFS;
> * raise an issue with the current source package on mentors;
> * respond to the substantive packaging topics in your e-mail.
>
> Logistics
> ---------
>
> (1) Can you confirm that [1] is the repository from which you generated
> the .dsc that you uploaded to mentors.debian.net? Can we work out of
> that repository from now on?
Yes.
> I want to be able to refer to git commits, and use `git diff` to review
> changes you've made in response to feedback. Using raw source packages
> is a pain.
>
> (2) It looks like we're going to need to package lots of library
> dependencies of the full chapel-runtime. I'm not going to be able to
> review and sponsor those -- it's too much for one volunteer. I will
> continue as the reviewer and eventual sponsor of the chapel source
> package itself (i.e. this RFS).
OK, thanks for letting us know. We'll seek other sponsors whenever
we start to pursue the other packages.
> Current source package
> ----------------------
>
> It fails to build, I think because it assumes $HOME exists, which is an
> assumption package builds cannot make (let me apologise that this is not
> better documented).
>
> I've attached a log.
We'll have a look. We're planning to patch `make check` to use /tmp
instead of $HOME for the Debian package.
> Responses to substantive packaging issues
> -----------------------------------------
>
> > Do you feel that we have addressed your concerns about the FHS?
>
> I think so! Three remaining issues:
>
> (1) Thank you for the explanation of the *.c, *.a, *.h files. Could you
> say what the *.py files are for? Again just part of the compilation
> process? Never expected to be run outside of that process?
The .py files are used to manage the Chapel configuration. The compiler
uses these scripts in order to determine the appropriate settings,
to include things like which tasking layer to use.
There is a utility, printchplenv, that prints out the current configuration
Reply to: