lpci

~cjwatson/lpci:test

Last commit made on 2022-04-21

Get this branch:: git clone -b test https://git.launchpad.net/~cjwatson/lpci

Only Colin Watson can upload to this branch. If you are Colin Watson please log in for upload directions.

Branch merges

Branch information

Name:: test

Repository:: lp:~cjwatson/lpci

Recent commits

7fd4c67... by Colin Watson on 2022-04-21

Empty test commit

	test:0 (build)
	build:0 (build)

2b951fc... by Colin Watson on 2022-03-29

Empty test commit

18d424f... by Colin Watson on 2022-04-19

Back to development

e5901d8... by Colin Watson on 2022-04-19

Release version 0.0.9

	test:0 (build)
	build:0 (build)

6f095bf... by Colin Watson on 2022-04-19

Ensure that parent of managed project path exists

https://code.launchpad.net/~cjwatson/lpcraft/+git/lpcraft/+merge/419463
broke lpcraft, because the project directory is now copied one level
deeper to `/root/lpcraft/project` but nothing created `/root/lpcraft`
first.

	test:0 (build)
	build:0 (build)

509724e... by Colin Watson on 2022-04-14

Fix handling of run-one --output-directory option

This was missed when the --output option was renamed to
--output-directory.

	test:0 (build)
	build:0 (build)

0c85067... by Colin Watson on 2022-04-14

Factor out _remove_prefix_if_possible function

	test:0 (build)
	build:0 (build)

aa6d0cc... by Colin Watson on 2022-04-14

Allow output.paths to reference parent directory

`dpkg-buildpackage` writes its output files to the parent directory of
the build tree. This is awkward to use with lpcraft, because
`output.paths` isn't allowed to escape the build tree.

We have to work with the world as it is, not as we'd like it to be, and
it doesn't seem unreasonable to allow gathering files from the parent
directory (but not further up the tree) in order to make things easier
for people integrating build systems such as this. Move the project
path inside the container one level down (to `/root/lpcraft/project`) to
support this.