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

standardizing pre-build maintainer actions



On Sun, Jun 10, 2007 at 08:40:21AM +0900, Junichi Uekawa wrote:
> > > I had an idea and still pondering on it.  I wanted to do automatic
> > > two-way synchronization with README.Debian and wiki.debian.org

I like the idea in general, but I would rather focus on ...

> [web->package]
> 
> 2. upstream FAQ page is updated through 'wget' into the package source
>    from time-to-time.

My feeling is that we, maintainers body, have in some packages the need
to do "stuff" before building a package, that this "stuff" often
encompasses accessing the network, and also that the result of "stuff"
needs to be committed in our versioning system (or at the very minimum
to become part of the new Debian source package we are going to upload).

A couple of example from packages I maintain:
- vim-scripts needs to download the HTML pages of all shipped addons in
  order to use them as user documentation available under /usr/share/doc
- vim needs to download upstream patches for micro releases which are
  stored in the source package and applied at build time

I guess a lot of us have similar needs. What about defining a
standardized debian/rules target which should take care of similar
stuff?

Once we have it one can imagine, for example, a CDBS rules file which
implement a dependency of this target as performing the one-way
synchronization asked by Junichi using a mapping from package names to
wiki pages, exploiting the docbook export, and so on and so forth ...

Comments?

-- 
Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
zack@{cs.unibo.it,debian.org,bononia.it} -%- http://www.bononia.it/zack/
(15:56:48)  Zack: e la demo dema ?    /\    All one has to do is hit the
(15:57:15)  Bac: no, la demo scema    \/    right keys at the right time

Attachment: signature.asc
Description: Digital signature


Reply to: