dids / clobber Goto Github PK

Since the packr2 utility is the primary culprit that increases the build time, it should we worth it if we bundle it with the application, or at the very least create a utility package that we can compile & run to do what we want.

Here's more documentation on bundling/embedding: https://godoc.org/github.com/gobuffalo/packr/v2/jam#Pack

I've heard reports that 3rd party drivers don't update (--ext-co isn't fetching updated packages?), but so far I've been unable to replicate, as ebuild.sh seems to actually just nuke any 3rd party package directories, then just clones them again.

Examination of the Clover pkg file made by Clobber reveals that OcQuirks.plist wasn't copied into it.

Not sure why this is, but it should be resolved. Thanks!

Related to: #19

Slice has moved Clover development to github. Clobber should be updated to match.

https://github.com/CloverHackyColor/CloverBootloader

Thanks!

Not sure if this is a clobber issue or due to me running it on Catalina.

( \ ( ) ( _ )( _\ ( \ ( _\ | `
| ( ()| | | ( ) || () )| () )| (()| () )
| | _ | | _ | | | || _ <'| _ <'| ) | , /
| (( )| |( )| () || () )| () )| (( )| |\
(/'(/'(_____)(/'(/'(_/'() ()
v0.3.3 by @Dids

✔ Verifying folder structure
✔ Verifying folder structure
✔ Verifying EDK is up to date
✔ Verifying Clover is up to date
✔ Building base tools
✔ Setting up EDK
◌ Linking nasm ⠼

Error: Failure detected, aborting

See the log file for more details:
/Users/shane/.clobber/logs/clobber.log
clobber.log

Instead of Finished in 1h4m4.286231541s, do something like Finished in 1 hour, 4 minutes and 29 seconds.

Currently --no-clean will both skip repo updates, as well as checking for any dirty files, which are technically two separate tasks and shouldn't really be available under a single option.

If each run creates it's own log file, we'll definitely want log rotation, otherwise we'll eventually run out of space.

Related to #6.

We're on v0.0.2 right now and it's still reporting v0.0.1.

This should be logged to the console and log. Additionally the CI should copy the last build log to the artifacts directory, for easy access later on.

• Copy clobber.log to CI artifacts directory
• Log edk2 commit
• Log clover commit
• Log macOS version
• Log Xcode version
• Log LLVM/clang version
• Log 3rd party driver commits (eg. AppleSupportPkg & friends)
• Add commit/version logs to the Clover installer package
• Push & tag a new version
• Restart any missing Clover builds on the CI

Doesn't seem to be pulling clover, just says it's downloading and returns me to the command prompt immediately.

`jam$ clobber

( \ ( ) ( _ )( _\ ( \ ( _\ | `
| ( ()| | | ( ) || () )| () )| (()| () )
| | _ | | _ | | | || _ <'| _ <'| ) | , /
| (( )| |( )| () || () )| () )| (( )| |\
(/'(/'(_____)(/'(/'(_/'() ()
v0.1.4 by @Dids

✔ Verifying folder structure
✔ Verifying UDK2018 is up to date
◌ Downloading Clover ⠹ :~ jam$ `

I’m planning to make some big changes to OcQuirks to support plist settings loading. As part of this, I no longer plan to include FWRuntimeServices.efi in the Release zip. Please pull it from Acidanthera’s AppleSupportPkg Release. I will maintain compatibility with this release version: https://github.com/acidanthera/AppleSupportPkg/releases

In addition I plan to add a default plist to the OcQuirks release zip that is to be located in the same directory as OcQuirks.efi itself. Please copy all the files from the release zip in order to support this. The proposed file structure will be a zip file containing a folder containing both OcQuirks.efi and OcQuirks.plist which will need to be moved to the appropriate location together.

For now, I am unable to make any changes to the OcQuirks release files as doing so breaks Clobber packaging entirely. I figured I would let you know my plans first before making breaking changes. Thanks!

There are quite a few different scenarios that we don't have parameters for.

• --build-only for building only (no update)
• --update-only for updating only (no building)
• --no-clean will skip deleting dirty files (currently also skips updates, but that'll change)

Anything else?

Ideally we'd want to have a build log written each time clobber is running, just so it's easier to debug any issues if (and when) they occur.

Especially on a clean install (brew remove clobber --force && brew install --force --HEAD clobber), it takes 2 minutes to install clobber, even on the most powerful of systems.

Either this means that the current formula is ignoring the vendor/ folder, or the packr2 binary installation is what's actually taking so long.

In any case, this needs to be resolved, as everything should be bundled with the project, then built and installed, which should definitely take less than a minute total (on average anyway).

• Fix dependency caching for Travis
• Fix dependency caching for Bitrise
• Fix dependency caching for Homebrew

Due to GitHub handle change (to lowercase) for long term purpose, go get may fail fetching github.com/Unknwon/com.
Please consider take some time to update it to github.com/unknwon/com in the go.mod file.
I truly apology for the inconvenience and unintended troubles caused.

For some reason the banner version when running clobber is not updated, and instead defaults to vx.x.x, which is incorrect.