[Piuparts-devel] Bug#700849: add more advanced usage tips to README

Ivo De Decker ivo.dedecker at ugent.be
Thu Feb 21 18:47:07 UTC 2013

Hi Holger,

On Mon, Feb 18, 2013 at 12:08:14PM +0100, Holger Levsen wrote:
> Subject: Bug#700849: add more advanced usage tips to README

> On Samstag, 26. Januar 2013, Ivo De Decker wrote:
> > Well, it would be nice to have some documentation to easily reproduce all
> > the tests you are running on the archive, even with packages that aren't
> > uploaded yet. This involves setting up a private repo and some wrapper
> > scripts. I don't know if such docs exist somewhere? I would be willing to
> > help with that.
> > 
> > Obviously, it would be a great help with that to have all your scripts,
> > even those that aren't in git (yet).
> > 
> > Currently, it's quite hard for random developers to do the piuparts tests
> > themselves, especially before upload. If they would just have to run some
> > script on their binaries (and wait quite some time for all the tests), that
> > would be one less excuse for not being piuparts-clean :)
> seems we should enhance the README with some more advanced usage tipps. The 
> manpage describes the needed options, but I agree an example in the README 
> would rock.

This is mainly what I meant by 'a wrapper around the piuparts command' in the
mail you quoted in bug 700848:

On Mon, Feb 18, 2013 at 12:05:15PM +0100, Holger Levsen wrote:
> Subject: Bug#700848: describe piuparts.d.o setup on about page
> On Samstag, 26. Januar 2013, Ivo De Decker wrote:
> > I added some info to https://wiki.debian.org/piuparts

> > As I noted in the wiki, it would be nice to have a single nice wrapper
> > which does most of this at once.
> a wrapper around the piuparts command? 

Having a script that just takes a package as argument and runs a number of
'standard' piuparts tests (install test, upgrade test, etc) would be nice.

As I wrote, I added some examples for that to the wiki, with a description how
to set up this environment, but it would probably be nice if someone reviewed
them to see if they make sense.

Also, we should agree on a single location to store this kind of information
(wiki.d.o, piuparts.d.o, the piuparts readme), so that it is easy to find.



More information about the Piuparts-devel mailing list