journald provides most of the same functionality, so aside from
some special cases it's redundant. It will probably get dropped
from @standard post f20, but for now get it out of the desktop
spin.
The periods in java-1.8.0-openjdk appear to cause a problem
with the exclude pattern matching. Using *s instead excludes
java-1.8.0-openjdk, but not java-1.7.0-openjdk.
openlierox doesn't build with lua 5.2. It may be a while before
it gets fixed. Upstream hasn't done a release in a long time.
(Though the discussions forums appear to be active.)
Someone noticed that I messed up the repo definitions for live images,
but the fix wasn't right for the live images. The install image uses
a source repo, but the live images don't. The repo commands for the
install image are in the install image itself. It is also safe to
include the updates repo since an updates repo is created for branched
that has no packages and stays that way until release is gold. That
way the same repo set can be used before and after release. Also a
commented out repo definition for updates-testing is provided to help
people who want to enable that.
If there are multiple tags pointing to HEAD we need to pick only
one. We'll take one that seems to be a version number. This allows
the version number tag to coexist with another tag, that perhaps
indicates which images it was used to build.
The previous system required making commits in order to do a new
build. This caused problems because we were using the git repo
directly for fedora builds and we couldn't use that exact version
when building matching packages because of needing to make new
commits in order to do the build.
Having the spec file in here also was unnecessary. It is easy to
just maintain the spec file in the Fedora package.
I still want to do a bit more future work with this to pick up
the version from a git tag.
Because pungi is an inclusive depsolver we can exclude some packages it
brings in and still get all of what we need. In particular we need to do
this to save space.
At one time only excludes on the repo commands were truly forced. It
had been the case that packages excluded in the %packages section
could still be included to satisfy dependencies. This is no longer the
case.
Doing the excludes in the packages sections allows us to list the
packages just once and it makes overriding the repo commands simpler
since the excludes don't need to be repeated.
