Skip to content
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

[TASK] Support of installation of a dependency via GitHub repo #2276

Closed
10 tasks done
alfoa opened this issue Mar 6, 2024 · 1 comment · Fixed by #2277
Closed
10 tasks done

[TASK] Support of installation of a dependency via GitHub repo #2276

alfoa opened this issue Mar 6, 2024 · 1 comment · Fixed by #2277
Assignees
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment

Comments

@alfoa
Copy link
Collaborator

alfoa commented Mar 6, 2024


Issue Description

Is your feature request related to a problem? Please describe.
I would like to set a dependency in the dependencies.xml file for a plugin using a GitHub repository url

Describe the solution you'd like
usage of pip functionality pip install git+https:url/to/github/repo for the installation of a dependency using the repository url

Describe alternatives you've considered
Manual installation


For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@alfoa alfoa added priority_minor task This tag should be used for any new capability, improvement or enanchment labels Mar 6, 2024
@alfoa alfoa self-assigned this Mar 7, 2024
@wangcj05
Copy link
Collaborator

issue closure checklist is good.

wangcj05 pushed a commit that referenced this issue Mar 11, 2024
* Support of pip installation of repo via pip. Closes #2276

* Update scripts/library_handler.py

* removed trailing whitespaces

* fixed syntax error

* In machine Centos os the enviroment setting is still done with Python 2..so f-stringed cannot be used

* same reason than before

* same reason than before

* added example 'documentation' in dependencies.xml file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants