Re: Potential MBF: packages failing to build twice in a row
On Thu, Aug 10, 2023 at 02:22:30PM +0200, Lucas Nussbaum wrote:
> > It might be worth to consider changing your workflow a bit and work with
> > a git repository. It does not have to be a clone of the repository (if
> > any) where the package is maintained, you can start with a fresh import,
> > e.g. with "gbp import-dsc".
> >
> > Then before building the package for the first time, commit or at least
> > stash your changes, and you can go easily back to a clean state with
> > "git reset --hard; git clean -fdqx".
>
> While this works in practice (and I do that as well), I find it hard to
> explain to new contributors that hacking on random packages requires
> them to create a temporary git repository so that they revert the
> package' source to a clean state.
They should be able to get an official git repo and hack on it instead.
Not now or in <10 years though, unless I guess you count dgit.
Reply to: