You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I would like building a debian package, I can use dget command to ge the sources.
I would like having a parameter to specify that the sources to be built must be download with dget (instead of having them in the git repo).
I see that under the hood it uses torizon/build-deb-action, so probably some new parameters is needed there, before
The text was updated successfully, but these errors were encountered:
@escherstair, our reusable workflow is based on jtdor/build-deb-action and it's crafted to build from the debianized (upstream code + debian dir) repo. Changing that would require a good amount of work and is not a need we have right now.
If you want to use it to build a package, you can always dget -x url/to/package.dsc, cd into the directory git add ., commit and then add this workflow. It should work correctly and build the package.
@charles2910 I jhad already added a request on the original jtdor/build-deb-action repo.
I don't expect that toradex takes care about such an implementation.
I think that using dget would be the most debianic way to get the sources of a debian package.
If you want to use it to build a package, you can always dget -x url/to/package.dsc, cd into the directory git add ., commit and then add this workflow. It should work correctly and build the package.
Is it possible to put the above steps in a github workflow?
Can you provide an example?
When I would like building a debian package, I can use dget command to ge the sources.
I would like having a parameter to specify that the sources to be built must be download with
dget
(instead of having them in the git repo).I see that under the hood it uses torizon/build-deb-action, so probably some new parameters is needed there, before
The text was updated successfully, but these errors were encountered: