Add west requirements.txt dependencies

---

gnu/packages/python-xyz.scm | 21 +++++++++++++++++++++

1 file changed, 21 insertions(+)

---

gnu/packages/python-xyz.scm | 16 ++++++++++++++++

1 file changed, 16 insertions(+)

---

gnu/packages/embedded.scm | 31 +++++++++++++++++++++++++++++++

1 file changed, 31 insertions(+)

peter@polidoro.io writes:

The linter picks up a couple of issues:

gnu/packages/python-xyz.scm:31761:17: python-canopen@2.0.0: sentences in description should be followed by two spaces; possible infractions at 47, 162

gnu/packages/python-xyz.scm:31759:15: python-canopen@2.0.0: invalid home page URL: ""

Plus, I'd avoid adding packages to the end of modules. If everyone does

this, it means lots of git conflicts. Instead, try and slot the new

package definition in somewhere close to related packages, or

alphabetically, or randomly even if neither of those approaches apply.

peter@polidoro.io writes:

The description looks like it could be improved here, plus same comment

about not adding new package definitions to the bottom of files.

peter@polidoro.io writes:

The description here also looks like it could be improved a bit.

Are you able to send some updated patches?

Also, when sending a few related patches, it's helpful if you get git

send-email to send them as a series, so something like:

git send-email HEAD~3

To send patches for the last 3 commits.

Christopher Baines <mail@cbaines.net> writes:

Thank you for your great suggestions, I will send updated patches

as soon as I get a chance.

I misnamed this patch series. I thought, at first, that I was

adding more dependencies to the 'west' package, but that is not

quite correct.

West is a Python tool that can help build Zephyr RTOS projects.

West is only optional for building Zephyr RTOS projects, though,

and much of its functionality could perhaps be replaced by Guix.

West provides a multiple repository management system, inspired by

Google's Repo tool and Git submodules. I think it would be much

more elegant to use Guix for managing the multiple repositories

and their dependencies instead of West. I do not yet know enough

about how the Zephyr ecosystem works, nor am I yet a good enough

Guix package writer, to figure out how to replace totally replace

West with Guix.

An intermediate step might be for me to create a simple Zephyr

package that installs the dependencies needed to build Zephyr

projects. Normally these dependencies are installed using apt

packages and Python requirements.txt files, as you can see in this

Zephyr getting started guide:

I am not yet sure how many dependencies I will need to write Guix

packages for and how long it will take. Should I just keep

emailing patches to this debbug number until I get to the final

zephyr package patch or is that annoying? Would you prefer I wait

until I have all of the packages figured out and then send them

all as one big patch series using git send-email as you suggested?

On a side note, do you happen to know how to setup git send-email

to work with pass, the standard unix password manager, instead of

the normal .git-credentials file? I would prefer not having my

password stored in a plain text file in my home directory. I tried

following this guide, but could not get it to work:

Thank you for your time!

---

gnu/packages/python-xyz.scm | 21 +++++++++++++++++++++

1 file changed, 21 insertions(+)

---

gnu/packages/python-xyz.scm | 19 +++++++++++++++++++

1 file changed, 19 insertions(+)

Hi,

peter@polidoro.io skribis:

Applied with the changes below (see

https://guix.gnu.org/manual/devel/en/html_node/Synopses-and-Descriptions.html).

Ludo’.

peter@polidoro.io skribis:

Applied, thanks!

Please open a new issue if there are followup patches.

Ludo’.