-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP π§ TO BE SPLIT UP: Some new features added #94
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like we're expecting users to include the hostname when installing packages with this change.
I don't think that's a breaking change we should be making right now. Can you refactor so we (continue to) default to github instead?
README.md
Outdated
@@ -52,6 +52,12 @@ Paste the following on your shell and you're good to go: | |||
$ curl -Lo- "https://raw.githubusercontent.com/bpkg/bpkg/master/setup.sh" | bash | |||
``` | |||
|
|||
Or | |||
```sh | |||
$ curl -Lo- "https://coding.net/u/hydra1983/p/bpkg/git/raw/master/setup.sh" | \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should suggest installing bpkg from your fork.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry about this, I will remove it :D
@@ -112,6 +118,22 @@ As a bonus, you can specify a **specific version**: | |||
$ bpkg install jwerle/suggest.sh@0.0.1 -g | |||
``` | |||
|
|||
Install from github directly | |||
```sh | |||
bpkg install "https://github.com/{user}/{project}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why include the host here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the host is not included, the line below will work
BPKG_REMOTES[0]=${BPKG_REMOTE-https://raw.githubusercontent.com}
It means the default behavior is still supported. And you can install from github as
bpkg install hydra1983/shlog ξ² 10:31  17-11-08
info: Install /hydra1983/shlog/master from remote https://raw.githubusercontent.com [https://github.com]
check: https://raw.githubusercontent.com
check: https://raw.githubusercontent.com/hydra1983/shlog/master/package.json?1510108773
fetch: https://raw.githubusercontent.com/hydra1983/shlog/master/package.json
write: /Users/edison/tmp/deps/shlog/package.json
fetch: https://raw.githubusercontent.com/hydra1983/shlog/master/shlog
write: /Users/edison/tmp/deps/shlog/shlog
shlog to PATH: /Users/edison/tmp/deps/bin/shlog
fetch: https://raw.githubusercontent.com/hydra1983/shlog/master/README.md
write: /Users/edison/tmp/deps/shlog/README.md
fetch: https://raw.githubusercontent.com/hydra1983/shlog/master/shlog.1
write: /Users/edison/tmp/deps/shlog/shlog.1
For this line
bpkg install "https://github.com/{user}/{project}"
It will not work until I refactored the code as the parsed repo and url is incorrect
Very good job ... thanks for these new features. I am also interested in using gitlab private repos with authentication by Personal Access Token. But we should review the construction of curls queries (authentication passed in parameter by specifying the curls -u or --header parameters for each repository type). Maybe another raw-oauth type in the BPKG_REMOTES strings ? |
It's sad that |
Great features, something we were discussing internally as well is to support other git locations and versions. @hydra1983 Do you have any plans to extend different versions by adding git tags or git commit tokens to the install command? Something like But I agree with other comments: the changes should not break current the bpkg behaviour but should be compatible with fallbacks etc |
What does actually break the current bpkg behavour, blocking this Pull Request ? |
@cha87de I think @mbl-35 It's long after my last commit. I may spend some time on a breaking changes list if I can got some spare time. And I need to fix the conflicts before this merge request can be accepted. In my plan, one new breaking change may be replacing Please verify the list below for the completion of the planed tasks.
Welcome for any suggestion. |
Any plan on fixing conflicts and merging? |
I can't speak for any of the other maintainers, but for me, this MR is too large and tries to add too many things all at once. Personally, I'd rather get the unit-tests and shellcheck issue sresolved (#72 and #78) and then break these changes up into smaller pieces (with tests) and merge them one thing at a time... |
@Potherca Good idea. :D. Here is an update and new plan.
|
Looks like there are lots of goodies here but I would love to see this broken up into smaller PRs π |
I've opened #116 to coordinate the effort to get these changes incorporated into the BPKG code-base. |
@Potherca Got it. Should I close this issue and working on the new issue? |
I've marked this pull-request as work-in-progress. We can leave it open for now, until all the work has been ported over into smaller PRs. |
bump #115 |
Any progress here? |
break mode
with option-b
for bothinstall
anduninstall
In
break mode
, global install and local install do the same thing which is going to download files to specified dirs.private
git repo is not considered to supportuninstall
command__load
func is added to import script from project and project dependenciesImport script from project
Import sciprt from project dependencies
${BASH_SOURCE[0]}
is required as I cannot find a better way to locate the script path at runtimeBPKG_LOG_LEVEL
instead ofLOG_LEVEL
BPKG_LOG_LEVEL="${BPKG_LOG_LEVEL:-${LOG_LEVEL:-2}}"
Personal Access Token
supportBPKG_LOG_LEVEL=1 bpkg install "raw-access|{gitlab_access_token}|https://{gitlabhost}/{group}/{project}@{tag}" -b
BPKG_PKG_PREFIX
to overwrite defaultdeps
dir