[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: intend-to-implement: script to obtain Debian Source



Hi,

> > | I second suggestion given at #250202 and like to see "unpacked" and
> > | "patched" targets to hit Policy 4.8.
> > 
> > If so, it should be «unpack» and «patch» to match the build and
> > install targets.
> 
> Note that there are existing packages that use 'unpack' and 'patch'
> targets for other meanings.
> 
> 
> unpack: some packages unpack the upstream tarball, some do patching
> patch: some patch the source tree, some generate patch out of it.

There are two points I would like happening:

1. A transitional software that does unpacking/patching using 
  heuristics/database approach; which I am intending to implement
  if noone has done yet.

  (how does lintian lab/xxxx/xxx.. do it right now?)

2. A policy on what target to have for optional unpacking and patching,
  and apply a recommendation that is enforced on etch/etch+1

  That should probably not be unpack/patch since they break existing 
  makefiles, and as #250202 suggests, unpacked and patched seem to be 
  good candidates.

  I'm going to check the output of 

  make -f debian/rules -n -p |  grep '^[^ ]\+:' | grep -v '^#' 

  to make sure what targets don't exist.


3. on etch+2, we may have a dpkg-supported solution usable.


regards,
	junichi
-- 
Junichi Uekawa, Debian Developer
17D6 120E 4455 1832 9423  7447 3059 BF92 CD37 56F4
http://www.netfort.gr.jp/~dancer/

Attachment: pgpOwz4QCYxPZ.pgp
Description: PGP signature


Reply to: