Workflow for developing PKGBUILDs #261

Open

opened 2022-06-23 08:39:51 +02:00 by Jef Roosens · 0 comments

Jef Roosens commented

2022-06-23 08:39:51 +02:00

Owner

The correct method for "testing" package builds is quite cumbersome. You have to push each change to the Git repository & then re-build it using vieter targets build. This in turn will download all dependencies every time. This just isn't practical.

It would be nice to have some system to develop PKGBUILDs locally, perhaps with the builder image not being removed every time & a way to mount the PKGBUILDs in the build container. #217 would be very useful for this as well.

The correct method for "testing" package builds is quite cumbersome. You have to push each change to the Git repository & then re-build it using `vieter targets build`. This in turn will download all dependencies every time. This just isn't practical. It would be nice to have some system to develop PKGBUILDs locally, perhaps with the builder image not being removed every time & a way to mount the PKGBUILDs in the build container. #217 would be very useful for this as well.

Jef Roosens added the

idea

label

2022-06-23 08:39:51 +02:00

Commenting is not possible because the repository is archived.