| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Resolves openbmc/openbmc#567.
Change-Id: I68e8e726f839038a6a256ff18a88d936ab0af3e4
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
| |
|
|
|
|
|
| |
Reduce the number of files to be updated after a
skeleton update from two to one.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Skeleton now invokes python setuptools to install its python
applications in a top level makefile, so a build time dependency
on native-python is required.
It should be noted that skeleton invoking python from make is
an interim thing until its python applications get their own
repository.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
This patch introduces a new abstraction 'skeleton-workbook'
for representing a system configuration. At present it is
pulled in by the skeleton recipe so the requirement on what is
implemented by a package providing obmc-phosphor-workbook is something
compatible with the existing System.py python modules in skeleton.
Additionally this patch adds a new recipe for each system using
a configuration file from skeleton today, and a class for common
configuration.
This enables a couple of things:
- No need to patch skeleton.service for each system.
- New systems don't have to put their configuration in the skeleton
repository.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
