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
Simplify installation of DAPS #581
base: main
Are you sure you want to change the base?
Conversation
We do not need these awkward steps with opening a browser etc. It's enough to pass the correct obs:// URI into "zypper addrepo" and zypper does the rest (finding also the correct architecture etc.)
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.
Generally looks an alot simpler, typo noted.
Co-authored-by: Stefan Knorr <sknorr@suse.de>
Thanks @sknorr for the feedback! Let me know if I should merge it after your approval. Another question: I've tried to adhere to the procedure structure. However, I'm wondering if we should maybe go a step further and completely avoid the procedure. I have something like this in mind: <para>
The quickest way to install &dapsacr; is using the <command>zypper</command> command.
Open a terminal and enter the following two commands:
</para>
<screen>&prompt.root;<command>zypper addrepo --refresh obs://&suse-dapsrepo; &suse-dapsrepo;</command>
&prompt.root;<command>zypper install --from &suse-dapsrepo; daps</command></screen> That way we avoid the (bulky?) procedure, but it would contain all the essential parts. I'm not sure if a procedure is here really needed. Thoughts? |
Please note that the obs:// thingie is an unsupported hack according to Adrian. |
Whaaat? Oh no! 😞 This is so convenient and short. Hope they fully support it someday. @adrianschroeter Is there a simpler way to do it? |
To be a bit more exact, obs:://$project lacks the information which OBS instance actually is intendended. Inside of an obs this syntax is okay, but everything which goes out (eg. the DISTURL) is using obs://$obsname/$project/... eg. obs://build.opensuse.org/openSUSE:Factory/.. . What zypper does is their decision, but it can not work atm with any other instance then the build.opensuse.org one. For everyone else (eg. SLE) it is broken. |
@adrianschroeter Thanks Adrian for your explanation! 👍 Much appreciated. This is not what I have anticipated, but well... 🙂 Currently, we have six steps to install daps. The steps are not really difficult, but cumbersome and error-prone: Procedure to install daps
Imagine how much easier it would be if we could just tell our readers to execute just one or two steps (in contrast to the six steps above). Maybe I missed it, but I haven't seen any simpler methods. Is there a chance to bless an (improved) |
After studying the manpage, it's also possible to use placeholders in URL. The above procedure could still be reduced to three steps, but with
|
Sorry to rain on your parade again, but this does not work with Tumbleweed. Also, it will not work for SLE. I think we need to come up with a technical solution for this problem rather than with a simple doc change. Is it possible to automatically generate a YMP file? |
A YMP file can include sections for multiple distributions at once. So we could just provide such a file (e.g. on the DAPS web site) and keep it up-to-date. |
Well, ... that's all nice, however, IMHO we should address this at a higher level. Zypper already provide a mechanism via the For the time being we need to circumvent that somehow, but I'd suggest to address this issue in zypper (via Bugzilla). |
I've created bsc#1181802. |
It is possible. Michael Andres gave me some helpful tips in the mentioned bug report. You need to modify just one file for Tumbleweed:
It is also possible for SLE. You need to modify the file |
Waiting for https://jira.suse.com/browse/PM-2464 to be resolved |
Our DAPS User guide contains a section "Installing DAPS on openSUSE". It contains 6(!) steps to install daps.
Although the steps are correct, there is an easier way to do. Instead of following all these six steps I was able to reduce it to three. It's enough to pass the correct
obs://
URI intozypper addrepo
and zypper does the rest (finding also the correct architecture etc.)