Hello,
On Thu, Jul 05 2018, Russ Allbery wrote:
> Reintroducing the same target with the same name but with a stricter
> definition would almost certainly make a bunch of those packages
> buggy. I'm dubious that it's worth disrupting whatever local workflow
> that they already have around get-or
On Fri, Jul 6, 2018 at 2:16 PM, Andreas Tille wrote:
> I fully share your view that the optimal situation would be if uscan
> would be some kind of wrapper around whatever code would be needed to
> create the source tarball. Since I share this view I once started to
> hack Files-Excluded into usc
Hi Russ,
On Thu, Jul 05, 2018 at 10:49:29AM -0700, Russ Allbery wrote:
> Andreas Tille writes:
>
> > My main point is that README.source is just text and no code that I can
> > run and test. That's different from my proposal.
>
> I can definitely see the merits of clear automation the process
Andreas Tille writes:
> My main point is that README.source is just text and no code that I can
> run and test. That's different from my proposal.
I can definitely see the merits of clear automation the process of
transforming an upstream release into a tarball usable for Debian
packaging (with
4 matches
Mail list logo
