This change separates the overlays for sysvinit and systemd builds.
- The inittab is overlayed if using sysvinit.
- /sbin/init is replaced by a script which calls the boot.d sequence and then execs /lib/systemd/systemd when using systemd.
When a package is added to the REPO any duplicates are supposed to be removed automatically.
The (package-name, version, arch) was determined by splitting the (fullpath) name by underscore.
If an underscore was present in any of the parent directories then the split did not yield
the correct information. As a result any duplicate packages were not removed and were instead
left in the REPO.
This fix splits the package basename instead of the package path.
You may now clone your ONL worktree as JEFF_IS_STUPID and it should work now.
Fix LED for MSN3800 system
Fix LED for systems with single-FAN drawer systems
Add kernel patches
Signed-off-by: Oleksandr Shamray <oleksandrs@mellanox.com>
- Fix the OnlPackageRepo lock.
The lock for the package repo has always been broken for some requests due to the nested nature of some of the calls.
This would cause the repo lock to be release prematurely in the middle of operations.
This becomes obvious once large parallel package builds are enabled.
The OnlPackageRepo class has been renamed to OnlPackageRepoLocked() and all locking has been removed.
All operations performed by the OnlPackageRepoLocked() class are now assumed to be non-concurrent.
The OnlPackageRepo class is now a wrapper around the OnlPackageRepoLocked class with acquires the lock
prior to requesting any operations. This change is transparent to the callers but ensures
that no nested locks (and premature unlocks) are performed.
- Improve the parallel makefile generation.
- Set pipefail to that targets fail even with the log tee.
- Allow packages with broken dependencies to set their stage explicitly.
- Parallel package builds require that the package cache be treated as read-only.
- Packages must specify their package prerequisites properly in their PKG file.
- In order to detect and correct this situation packages will no longer
be implicitly built as part of calls to onlpm find and link operations.
We may be able to relax this restriction once the build is tight.
- Package Cache Corruption
- If the package cache is corrupt (usually due to an aborted operation) then it we will
automatically rebuild it instead of just whining about it.
Makefiles that call $(shell onlpm --find-file *) have always failed poorly
when the file cannot be found.
The onlp_find_file template can be called to both assign and check the
results. If an error occurred in getting the value then a Makefile error is raised.
Specifying useful package fields has been historically pretty lazy since most systems have been built as self-contained images without dynamic package updates.
This commit hopes to improve the situation.
The recommended package organization for ONL and for systems built with ONL as the base follow the pattern of $project/packages/base/$arch/* and $project/packages/platforms/$vendor/$arch/
The heirarchy of directories in which the packages reside also provide a natural inheritence heirarchy for debian package fields.
This property is now exploited to allow default package keys to be specified base on their location in the filesystem heirarchy as follows:
Before a PKG.yml file is evaluated its parent directory heirarchy is traversed looking for either or both of these files:
PKG_DEFAULTS.yml -- This is an onlyaml file which can specify the values of package keys.
PKG_DEFAULTS -- If this file is executable it is expected to output valid yaml containing package keys.
All of these values are then combined in reverse order to provide a default dict for the package.
Example usages:
- Fields global to all packages in the project (like Vendor, Maintainer, Version [for coherent builds], maintainer, etc) can be specified in the top-most PKG_DEFAULTS.
- Archicture can be specified in the $arch/PKG_DEFAULTS.
- Platform Vendors can specify their information at the top of their platform directory.
By specifying your own PKG_DEFAULTS you can coexist the ONL versions and your own version without ineheriting any of the defaults from ONL itself.
These are only the defaults for keys not specified in the PKG file. You can still obviously override every field in each package declaration.
The ONL package files will be updated in a separate commit to use this new hierarchical approach.
Package version numbers, copyrights, and general information fields have all
