Skip to content

Conversation

EmilioPeJu
Copy link
Contributor

The IPK package will be used in the yocto rootfs.

Copy link

@coretl coretl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess that creating ipk files is manual. That seems to have an annoying amount of boilerplate, and will be used in at least 3 repos. I suggest:

  • Putting control as a flat text file in the root of the repo (maybe named ipk-control?)
  • Making a python package called ipk-build package on pypi that has a single ipk-build entrypoint that does the same as this script
  • Installing it into the devcontainer along with all the other python deps
  • Calling it from the makefile in this repo and other places that need to make ipk files

Please can you prototype this as a single python script ipk-build.py in this repo and we'll take it from there

@EmilioPeJu
Copy link
Contributor Author

Hi @coretl, the reason I did it this way is to avoid adding more dependencies, if you prefer to do so, we should use the project opkg-util which was made for this task.

@coretl
Copy link

coretl commented Sep 2, 2025

I suggest adding it as a submodule and calling it from there then (it doesn't seem to be published on pypi)

@EmilioPeJu
Copy link
Contributor Author

EmilioPeJu commented Sep 2, 2025

OK, I've done a similar change to the one in the FPGA repo, the packaging related files are under packaging including the new submodule. The zpkg related part has been removed as requested, this doesn't allow to remove the PandABlocks-rootfs dependency because of some github-release script.

@EmilioPeJu EmilioPeJu force-pushed the yocto-pkg branch 4 times, most recently from 850b2fc to e5ec639 Compare September 3, 2025 00:04
@coretl
Copy link

coretl commented Sep 3, 2025

The zpkg related part has been removed as requested, this doesn't allow to remove the PandABlocks-rootfs dependency because of some github-release script.

I think that script is only used in this repo, because all the other GitHub releases are made by CI in GitHub. This is the only one that requires pushing locally, so unless you can find any other references in other repos you can move that script to this repo.

The advantages are:
- The ipk build script is smaller.
- The metadata is validated.
The disadvantage is having an extra dependency which in this case is in
the form of a submodule.
@EmilioPeJu
Copy link
Contributor Author

Done! it turned out that make-githu-release.py was removed from panda rootfs, I had to copy it from an old commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants