Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move DTS to a separate repository #773

Closed
macpijan opened this issue Apr 3, 2024 · 3 comments · Fixed by Dasharo/dts-scripts#1 or Dasharo/meta-dts#115
Closed

Move DTS to a separate repository #773

macpijan opened this issue Apr 3, 2024 · 3 comments · Fixed by Dasharo/dts-scripts#1 or Dasharo/meta-dts#115

Comments

@macpijan
Copy link
Contributor

macpijan commented Apr 3, 2024

Maintenance of DTS script under meta-dts is not optimal. It is difficult to manage this DTS tool independently. Meta layer should focus on metadata for the build, not on the specific implementation. When separated, the DTS scripts can be more easily unit tested, also in CI, without the necessity of full Yocto integration.

Preliminary work, preserving the history, has been already done here: https://github.com/Dasharo/dts-v2

Next steps:

  • move around files and clean up this repository from yocto metadata, leaving manageable structure for scripts
  • provide Yocto recipe in meta-dts, including this repository,
    • in the same MR, remove the dts scripts from meta-dts
@DaniilKl
Copy link
Contributor

DaniilKl commented Apr 8, 2024

@macpijan, shall we change the new repository name, e.g. to dts-scripts? dts-v2 is not a clear name as for me.

@DaniilKl
Copy link
Contributor

DaniilKl commented Apr 8, 2024

@macpijan, seems like the new repo is not properly set up, I cannot push branches:

λ git push origin yocto-cleanup 
ERROR: Permission to Dasharo/dts-v2.git denied to DaniilKl.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

@macpijan
Copy link
Contributor Author

macpijan commented Apr 8, 2024

@DaniilKl

seems like the new repo is not properly set up, I cannot push branches:

Should be fixed now.

shall we change the new repository name, e.g. to dts-scripts? dts-v2 is not a clear name as for me.

We might move it back to dts but I wanted to first ensure we move everything from the old repo. I would not worry too much about the repo name now, it is very easy to change it.

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