Re: Bug#515856: Debian Policy 220.127.116.11 released
- Date: Wed, 11 Apr 2018 13:54:58 -0700
- From: Russ Allbery <rra@xxxxxxxxxx>
- Subject: Re: Bug#515856: Debian Policy 18.104.22.168 released
Ian Jackson <ijackson@xxxxxxxxxxxxxxxxxxxxxx> writes:
> (ii) You make a very good argument that policy should continue to give
> guidance for this kind of situation. The target should probably be
> put back in policy, but with an explicit note saying it's not normally
> desirable, or something.
I think the Policy guidance is that you should document your maintenance
procedures in README.source if they're unusual, which would include this.
In that documentation, you can reference whatever scripts or targets would
be involved in doing an update.
I'm dubious there are really that many cases where knowing about a
get-orig-source target is the *only* piece of additional information
required about a source package and everything else is entirely standard.
I would expect somewhat non-standard upstreams to need at least some
additional explanation (how to choose a good upstream commit to package,
I see that the current wording in Policy about README.source doesn't call
out this case (upstream updates) explicitly. Maybe it should.
I'm pretty reluctant to specify this sort of optional target that works
differently in every package that uses it back in Policy because it's
really not standardized, nor do I think it's possible to standardize. If
we really want to write something down about the target, maybe the
Developer's Reference would be a better spot? There were a whole host of
issues with having this in Policy that were resolved by moving it outside
the scope of Policy, such as how to document dependencies required for
running the get-orig-source target.
Russ Allbery (rra@xxxxxxxxxx) <http://www.eyrie.org/~eagle/>