search

avocado-framework / avocado

Avocado is a set of tools and libraries to help with automated testing. One can call it a test framework with benefits. Native tests are written in Python and they follow the unittest pattern, but any executable can serve as a test.
https://avocado-framework.github.io/
Other
342 stars 340 forks source link

Add debian folder #5912

Open dnegreira opened 5 months ago

dnegreira commented 5 months ago

Add a debian folder to build avocado-framework as python3-avocado-framework package on Ubuntu. Currently the debian/copyright file needs a review, among other things to be improved before a final commit.

This commit is meant to be reviewed by upstream maintainers of avocado-framework and work on improvements and pieces missing, so that we can squash and do a proper commit at a later stage.

Related: #5911

clebergnu commented 5 months ago

Hi @dnegreira, thanks for this! It's very welcome addition.

It looks like the CI issue can be solved simply by a rebase (this branch is like ~90 commits behind Avocado's own).

dnegreira commented 5 months ago

Hi @clebergnu, Thanks for your input; I have rebased and force-pushed. I'm also looking for your comments on my questions. Of course, if you have any other questions or concerns, let me know.

clebergnu commented 4 months ago

Hi @clebergnu, Thanks for your input; I have rebased and force-pushed. I'm also looking for your comments on my questions. Of course, if you have any other questions or concerns, let me know.

@dnegreira let me know if I'm missing any answer to you. Thanks!

dnegreira commented 4 months ago

Hi @clebergnu Just need your input on the two above threads I have open

clebergnu commented 3 weeks ago

Hi @dnegreira ,

I see you're updating the work on this PR! Thanks a lot.

I'd appreciate also a few hints on how to test the generation of the packages in a way that matches your workflow.

Thanks again!

dnegreira commented 3 weeks ago

Hi @clebergnu

Thanks for keeping an eye, we are almost there. Currently, we have a target to push this and get into Debian unstable/testing as well, so that we can get it imported into Ubuntu and maintain the package on both distros.

I'd appreciate also a few hints on how to test the generation of the packages in a way that matches your workflow.

Should I add an entry to the Readme file? Should I also expand the Makefile.pkg to add a target to build a .deb package, or add a separate script to help build the package?

clebergnu commented 2 weeks ago

Hi @clebergnu

Thanks for keeping an eye, we are almost there. Currently, we have a target to push this and get into Debian unstable/testing as well, so that we can get it imported into Ubuntu and maintain the package on both distros.

I'd appreciate also a few hints on how to test the generation of the packages in a way that matches your workflow.

Should I add an entry to the Readme file? Should I also expand the Makefile.pkg to add a target to build a .deb package, or add a separate script to help build the package?

Yes, and yes! And many thanks!