| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Also, allow the hardcoded URLs to override the one provided by the
metadata in rubygems.org, because that is sometimes incorrect.
|
| |
|
|
|
|
| |
I have realised now that the tool needs to manually search for and
load all gemspecs in the repo, because the Gemfile doesn't necessarily
include them.
|
| |
|
|
|
| |
These allow me to focus on getting the right source URLs for everything
first off.
|
| | |
|
| |
|
|
| |
This mostly consists of indenting things by 2 spaces.
|
| |
|
|
| |
rubygem.to_chunk has changed a bit.
|
| |
|
|
|
|
|
| |
This is hopefully useful for when errors are encountered in packages
that the user didn't expect the code to be importing. Just saying 'I
had a problem with this package' isn't enough when the actual error
may be further back, in the dependency detection.
|
| |
|
|
|
|
|
|
|
| |
However, the Gemfile for Rails lists a bunch of stuff that's perhaps
required for all of Rails, but is *not* required for some of the
Gems such as ActiveSupport.
Is this a bug in Rails' Gemfile? Should we ignore the Gemfile and just
look at the individual .gemspec files?
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This generates a chunk morph for ONE gem defined in a given git
repository.
It has one known issue: where gems are nested in a source repo (as is
the case in rails) they will not be found. The `bundle install` command
does find them, so clearly something is up with the way I am hacking the
'bundler' library around.
Also, there is lots of inheritance and method override hacking :(
|
| |
|
|
|
|
|
|
|
|
| |
This generates a stratum and a set of chunk morphologies for integrating
a given RubyGem project into Baserock. It uses the 'bundler' Gem to
collate the list dependencies. This means that it works for any Gem that
has a "Gemfile", and will also honour the "Gemfile.lock" file created by
Bundler if the file exists.
It requires the new 'rubygem' build mode.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This build mode honours the new 'gem-url' field. It downloads the
Gem from the given URL
Including code from random servers on the internet in your builds might
mean that you can't reproduce what you build from source later on,
because the file or even the whole server might be gone. Morph does
nothing to prevent this, either for Git source code or Ruby Gems.
The Trove server provides a way of mirroring Git repos on local
infrastructure, so organisations can be certain they won't disappear
later on and so that they are quicker to access. Trove does not yet
provide a similar service for mirroring the required RubyGems.
|
| |
|
|
| |
Add staging_area.copy_file_to_build_dir() function. Use with care!
|
| |
|
|
|
|
|
|
| |
This could just as easily be a generic 'extra-build-data' field, which
could be used to download arbitrary files into the build chroot. Making
it easier to include random data from the internet in builds is not
really a step forward for a tool that tries to encourage reproducability
from source, however.
|
| |\
| |
| |
| |
| | |
Reviewed-By: Adam Coldrick <adam.coldrick@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | | |
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
Reviewed by: Richard Maw <richard.maw@codethink.co.uk>
Merged by: Francisco Redondo Marchena <francisco.marchena@codethink.co.uk>
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
Reviewed by: Richard Maw <richard.maw@codethink.co.uk>
Merged by: James Thomas <james.thomas@codethink.co.uk>
|
| | |\ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Remove the BOOTLOADER environment variable and instead favour
BOOTLOADER_CONFIG_FORMAT to set the desired bootloader format, and
BOOTLOADER_INSTALL to set the type of bootloader to install.
For example, since u-boot can boot using extlinux.conf files, it's
conceivable that someone might want to do CONFIG_FORMAT=extlinux.conf,
INSTALL=u-boot.
However, for most platforms you would want to set INSTALL to "none"
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | | |
Reviewed-by:
Richard Maw
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Instead of leaving morph3 with a potentially confusing name, rename it
to `morphology` since it is now the only implementation of the
Morphology class.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 4124c50b8dc3dfb0ffb933153d0fe6385edf389c.
This commit is no longer needed now that morph2 is gone.
Conflicts:
morphlib/cachekeycomputer.py
|
| | | |
| | |
| | |
| | | |
This commit removes the now unneeded morph2 and its associated tests.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Update the edit-morph script used in the test suite to use morphloader
for saving/loading morphologies rather than morph2. Also remove some
unused code.
|
| | | | |
|
