Re: Package's inputs for developer?

[zimoun <zimon.toutoune@gmail.com>]

Hi,

On Tue, 8 Mar 2022 at 17:45, Olivier Dion <olivier.dion@polymtl.ca> wrote:
> On Tue, 08 Mar 2022, zimoun <zimon.toutoune@gmail.com> wrote:

> I had more a recommended workflow in mind.  For example, I have a bunch
> of scripts under `tools/` for compiling and testing the project within
> Emacs.  And they all use these developer inputs.  I find this useful if
> for example someone wants to quickly debug the program from source
> without searching too much on how to do so.  Just fire your text editor
> and voila.

If 'tools/' is a directory from upstream, then maybe the
recommendation would be to directly add a guix.scm file containing the
material for jumping in development.


> >     guix shell gdb lcov -D my-package
> >
> > and if it is often the same set of packages, I use a manifest.
>
> Yes this is what I also but I wrapped it in a script.  And how do you
> indicate the "-D" in your manifest?

Well, 'package-development-inputs' from (guix packages) should fit the
job, I guess.


Cheers,
simon