rpm-ostree

Author SHA1 Message Date

Author	SHA1	Message	Date
Colin Walters	a3769a7219	vmcheck: Experiment with the name `nxs` I find myself not liking the name rpm-ostree anymore; it's descriptive, but unfortunately we compete with other projects with easier and sexier names. Also, people continually find the ostree and rpm-ostree layering unclear. It's much easier to say "nxs depends on ostree", even though textually it's obvious "rpm-ostree depends on ostree". Anyways, just an experiment for now. Closes: #307 Approved by: giuseppe	2016-06-08 14:26:08 +00:00
Colin Walters	77eb3e2b5b	tests: Introduce "vmcheck" This is infrastructure that's oriented around Vagrant, we do builds inside the target VM (actually inside a Docker container), but then directly `make install DESTDIR=/host/`. The goal here is to have a convenient workflow for: - dev -> hand testing - dev -> run destructive tests Closes: #303 Approved by: jlebon	2016-06-07 18:39:46 +00:00

Colin Walters

a3769a7219

vmcheck: Experiment with the name nxs

I find myself not liking the name rpm-ostree anymore; it's
descriptive, but unfortunately we compete with other projects with
easier and sexier names.

Also, people continually find the ostree and rpm-ostree layering
unclear.  It's *much* easier to say "nxs depends on ostree", even
though textually it's obvious "rpm-ostree depends on ostree".

Anyways, just an experiment for now.

Closes: #307
Approved by: giuseppe

2016-06-08 14:26:08 +00:00

Colin Walters

77eb3e2b5b

tests: Introduce "vmcheck"

This is infrastructure that's oriented around Vagrant, we do builds
inside the target VM (actually inside a Docker container), but then
directly `make install DESTDIR=/host/`.

The goal here is to have a convenient workflow for:

  - dev -> hand testing
  - dev -> run destructive tests

Closes: #303
Approved by: jlebon

2016-06-07 18:39:46 +00:00

2 Commits