| Age | Commit message (Collapse) | Author |
|---|
|
Kconfiglib/* were under ISC license before they were imported
here from https://github.com/ulfalizer/Kconfiglib
Adjusting SPDX header to reflect that fact.
tools/* all have some sort of GPLv2 headers; adding SPDX header
to make it obvious.
This address bug #13334 :
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13334
Change-Id: I243f2dd266a398f982798b771e74a67be70ecb52
Signed-off-by: William Bourque <wbourque@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Recent changes to scc/spp process .scc files and generate meta-series
that are in a slightly different location. With this commit we can once
again process an entire kernel-cache and produce a branched and
populated git tree.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
To cover corner cases that are more apt to show up when doing
treegen and when $META != meta/
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
It turns out to be inevitable, and just annoying when making
a tree from several hundreds of patches.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Previously the meta directory was added to all .gitignore files, otherwise
all users of the kernel would see an untracked directory "meta". This
caused workflow issues, since the same .gitignore was shared on the meta
branch itself. Which meant that changes were not shown and files needed to
be added with the -f flag.
To fix this, we teach the tools to look for .$META as the meta data
container, and place the meta branches directory under that same name.
The result is that the .meta directory is ignored by git automatically, but
is available to all branches. And switching to the meta branch no longer
warns of clobbered files, and once you arrive, files are tracked and
manipulated normally.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Use new command line option and existing KMETA env var where
appropriate.
Also disable autoresume in order to speed up treegen patch
pushes. ($sname vs. "-a" flag).
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
To support inhibiting of configuration values via include directives,
it must happen in a depth first based processing mode. The existing
monolithic processing of files, which then generate a script, that
generates a meta-series work in a model where all files are found,
individually processed and then re-assembled to generate the file output.
To allow enhanced processing of includes, we break the processing into
two parts, while keeping the output identical to the existing outputs
of the scripts. The first phase preprocesses the target files, in a
depth first manner, expanding included files, and converting kernel
configuration and patch directives to absolute paths (while performing
checks on their existence). The second phase, consumes the preprocessed
file, and generates a meta-series for future processing.
The logic and output of the existing scc processing is maintained, but
is now faster, robust and can handle more complex conditioning of the
input files.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The list of tools captured in the meta directory of a new repository
was missing some recent addition. With this change, all tools used
to construct, configure and build a kernel are copied into the
meta/scripts directory during repository creation.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When generating a tree, it is (unfortunately) common that the
base tree doesn't contain the tag that the user thinks it does.
In this case, we should abort the tree generation and report a
clear error.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
kgit-init copies the kern-tools scripts and intends to copy createme.
The typo is in the usage() of updateme as well.
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
|
|
The ability to run kgit-init against a remote repository is unused,
and it is reasonable to expect that a build system / fetcher should
be used to ensure that the repository being used is local the location
where it will be built. As a result, we can remove support from the
script.
Secondarily, a safe default content branch of 'master' is chosen, since
it will exist in all repositories.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
In order to cleanup/clarify the initialization process, it is best
to checkout branches quietly, and only create the meta branch
when required.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
It isn't always desireable that kgit-init create branches and
commits, in particular when a custom repository is being used
that may or may not contain existing branches. If content is
not supposed to be created, the repository is conditioned and
staged, but no branches or commits are created.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The 'meta' branch can have many names, but when it is called
'meta' the subdirectory meta/cfg/meta/, simply looks like a
mistake. This is renamed to meta/cfg/scratch/ to indicate its
actual use .. a scratch location for building the meta series.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The existing branch and meta data storage was tightly
coupled to the existing naming scheme. In order to support
a more transparent branch hierarchy, changes are required
to the scripts that manage the tree.
Note: These changes are not backwards compatible with
old trees.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Create the smallest set of kernel tools required to checkout,
build and manipulate Wind River Linux kernel.
Details of the usage are in the indivdual scripts, but generally
speaking these are never excuted directly by the end user
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
William Bourque
Bruce Ashfield
Paul Gortmaker
Bruce Ashfield
Michel Thebeau
bruce