Commit d580884e4b605f39e87d184e28ada0ce766fd0c0 - rust-libslirp

Update instructions to be more detailed Ximin Luo 5 years ago

3 changed file(s) with 24 addition(s) and 8 deletion(s). Raw diff Collapse all Expand all

-0

README.rst less more

	0	Instructions
	1	============
	2
0	3	Run ``./update.sh <rust-crate-name>`` and follow its instructions.
1	4
2	5	(The above applies even for new Rust Debian packages.)
3	6
4	7	For now, the script assumes you cloned and built debcargo in ``../debcargo``,
5	8	so do that once before you run it.
	9
	10
	11	TODO
	12	====
	13
	14	maybe use --copyright-guess-harder

-1

release.sh less more

16	16	git diff -q -- "$PKGDIR_REL" \|\| \
17	17	abort 1 "cannot release, update resulted in git diffs to $PKGDIR_REL"
18	18
19		git commit -m "Update package $PKG"
	19	git commit -m "Release package $PKG"
20	20
21	21	( cd "$BUILDDIR" && dpkg-buildpackage -d -S --no-sign )

+14

-7

update.sh less more

3	3
4	4	if [ ! -d "$PKGDIR/debian" ]; then
5	5	mkdir -p "$PKGDIR/debian"
6		sed -e 's/^#overlay =/overlay =/' -e '/^#/d' "$DEBCARGO_GIT/debcargo.toml.example" > "$PKGCFG"
	6	echo 'overlay = "."' > "$PKGCFG"
7	7	touch "$PKGDIR/debian/copyright"
8	8	git add "$PKGDIR"
9	9	fi

20	20	Automatic update of $PKG finished; now it's your turn to manually review it.
21	21
22	22	Deal with any FIXMEs mentioned above, by editing the corresponding source files
23		in $PKGDIR_REL (and NOT the build directory as mentioned). When done, git-add
24		your changes and re-run this command (\`./update.sh $*\`).
	23	in $PKGDIR_REL - and NOT the build directory as mentioned. If a hint file is
	24	listed, indicated by (.), you should edit the NON-hint file, without the
	25	suffix .debcargo.hint, and git-add the hint file exactly as output by debcargo.
	26	So for example to deal with a FIXME in build/PKG/debian/copyright.debcargo.hint
	27	you should edit src/PKG/debian/copyright.
25	28
26		Check that your fixes actually get rid of the FIXMEs. Of course, you may ignore
27		FIXMEs listed in hint files, indicated by (.), assuming you actually fixed the
28		issues in the corresponding non-hint files. (We have no way to auto-detect this
29		so you have to be honest!)
	29	When done, git-add your changes plus any unmodified hint files, and re-run this
	30	command (\`./update.sh $*\`).
	31
	32	Check that your fixes actually get rid of the FIXMEs. Of course, you can ignore
	33	FIXMEs listed in hint files, assuming you actually fixed the issues in the
	34	corresponding non-hint files. (We have no way to auto-detect this so you have
	35	to be honest!) You should also ignore the FIXME in the Distribution field in
	36	the top entry of debian/changelog, that will be dealt with in the next step.
30	37
31	38	If satisfied with the output, run \`./release.sh $*\` to finalise your changes
32	39	in the changelog and build a release-ready .dsc in build/. Assuming it runs