.deb and .rpm installation commands fixed

[renich]

It seems the documentation assumed that woodpecker had only one package.

Now, it sets a more complete example by:

• defining an example RELEASE_VERSION variable.
• using the variable across the commands.
• installing all three packages. (maybe cli and agent aren't required, but agent is referenced in the following documentation)

In any case, the commands now actually work.

[xoxys]

Thanks! I just added a one-liner to auto-capture the latest release.

[xoxys]

Could you please also adjust the next docs in https://github.com/woodpecker-ci/woodpecker/tree/main/docs/docs?

[renich]

Could you please also adjust the next docs in https://github.com/woodpecker-ci/woodpecker/tree/main/docs/docs?

Yep, sure thing. Taking a look at it right now.

[renich]

I think we got into more trouble by suing the ${RELEASE_VERSION#v} form. Would you reconsider?

[renich]

Feel free to revert that last commit (obtaining the version) if you don't like it.

Let me know if you'd reconsider on using the initial version of $RELEASE_VERSION or if you want to stick with ${RELEASE_VERSION#v}.

[xoxys]

I think we got into more trouble by suing the ${RELEASE_VERSION#v} form. Would you reconsider?

Can you explain this a bit more?

[renich]

I think we got into more trouble by suing the ${RELEASE_VERSION#v} form. Would you reconsider?

Can you explain this a bit more?

When we use the ${RELEASE_VERSION#V} version, you have to use that multiple times in the download scripts. It's a subtle change and harder to grasp since it's not common.

On the other hand, if we use ${RELEASE_VERSION}, we only have to add a "v" in the download link and that's it. We're free to use the variable as is for the rest of the commands.

In my opinion, the latter is a tad bit more straight forward and non-confusing.

[xoxys]

Works for me, lets do it that way :)

[xoxys]

Thanks again.

[woodpecker-bot]

Deployment of preview was torn down