Skip to content

Add a helper for easier sourcing from development repos聽#1449

Description

@tewalds

馃搶 Task summary

source < (curl ...) should have configurable repo and branch.

馃搵 Task details

Every ct script starts with:

source <(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/misc/build.func)

but when you're developing it has to go to ProxmoxVED or to your own branch. You may point to your branch properly, but if you didn't modify all instances across the codebase it will point to the original and miss your install/*-install.sh changes. If you're lucky you get an uninformative curl 404 error, and otherwise you end up with the old version. Either way, you get no indication of what was requested, leading to indecipherable and inexplicable errors.

I'd like to suggest all instances of

source <(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/...)

should be replaced by something like

source <(proxmoxve_source misc/build.func)

which can be configured by SOURCE_REPO and SOURCE_BRANCH, so that you don't need to modify hundreds of files. Maybe the first one needs the full path, but at the moment you need to modify all files, and this could be mitigated pushing it to a configuration variable that can be set from the cmdline.

Activity

  1. michelroegl-brunner commented on Feb 11, 2026

    @michelroegl-brunner
    Member

    You can do a Pull Request in the DEV repo if you like. We had many attempts wich tryed to fix that, but nothing ever worked. So it is not high on our TODO list at this moment.

  2. heinemannj commented on Feb 13, 2026

    @heinemannj
    Contributor

    but when you're developing it has to go to ProxmoxVED or to your own branch. You may point to your branch properly, but if you didn't modify all instances across the codebase it will point to the original and miss your install/*-install.sh changes. If you're lucky you get an uninformative curl 404 error, and otherwise you end up with the old version. Either way, you get no indication of what was requested, leading to indecipherable and inexplicable errors.

    @tewalds 馃憤
    I'm facing this kind of issue on a regular base ...

    For sure, there are workarrounds mentioned above - but I have the strong feeling that a lot of people trying to support this project giving up after a couple of hours without any success.

    @ALL: Let's try together and hopefully there is a way to simplyfy.

  3. tewalds commented on Feb 13, 2026

    @tewalds
    Author

    I spent a literal day trying to understand why nothing worked until I figured this out, and it's still painful testing it every time since the code has to refer to itself, which also makes it unsubmittable. I don't think I'll be contributing again until this is fixed. It's not worth the effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions