Using Snapper to undo changes #232
Conversation
| <description>For more information</description> | ||
| </resource> | ||
| <resource xml:id="_snapper-undo-changes-compare-undo-and-rollback" href="../glues/snapper-undo-changes-compare-undo-and-rollback.xml"> | ||
| <description>For more information</description> |
There was a problem hiding this comment.
Not that it matters, but "For more information" isn't the proper description for this glue topic?
There was a problem hiding this comment.
Very nice topic! The only issue that I have is with the links to non-existing sections or yet-to-be-written articles. Even if they are resolved one day, the disrupt the flow and might make readers jump from this article and never come back.
Only add those links when the reader absolutely needs this reference to proceed with what you're describing. Otherwise put'em right to the end of the article under "For more info".
There was a problem hiding this comment.
Either keep out of the article until you have something to point to or activate this section and let it point to the respective sections in the legacy docs.
There was a problem hiding this comment.
Great job!
As with the first piece, I'm having issues with the sheer abundance of links leading out from the article from pretty much any point. I suggest reviewing every single one of them and trying to determine whether they are needed at that time at all or whether they'd work better at the end.
The article starts a bit out of the blue. It doesn't really have a proper intro that gently states what the thing is all about.
That's about all I could find. Looking forward reading to the entire set of snappery Smart Docs!
| <screen> 1 <?xml version="1.0" encoding="utf-8"?> | ||
| 2 <snapper-zypp-plugin-conf> | ||
| 3 <solvables> | ||
| 4 <solvable match="w"<co xml:id="zypp-conf-match"/> important="true"<co xml:id="zypp-conf-important"/>>kernel-*<co xml:id="zypp-conf-kernel"/></solvable> | ||
| 5 <solvable match="w" important="true">dracut</solvable> | ||
| 6 <solvable match="w" important="true">glibc</solvable> | ||
| 7 <solvable match="w" important="true">systemd*</solvable> | ||
| 8 <solvable match="w" important="true">udev</solvable> | ||
| 9 <solvable match="w">*</solvable><co xml:id="zypp-conf-packages"/> | ||
| 10 </solvables> | ||
| 11 </snapper-zypp-plugin-conf></screen> |
There was a problem hiding this comment.
If you add line numbers to a screen you get these disadvantages:
- Users can't copy and paste your content.
It leads to invalid XML and the user has to edit it after it has been copied. Very user unfriendly. - You does the job of the stylesheets
There is no need to repeat this tedious task. Delegate it to the stylesheets! 😉 They can do this task.
So please avoid it, don't do it manually.
The recommended way would be this snippet:
<screen linenumbering="numbered">This would instruct the stylesheets to number each line. However, due to some technical issues, this is currently not supported by xsltproc. 😞
There was a problem hiding this comment.
Additionally, it would be nice to see an example with match="re".
| With this configuration snapshot, pairs are made whenever a package is | ||
| installed (line 9). When the kernel, dracut, glibc, systemd, or udev packages | ||
| marked as important are installed, the snapshot pair will also be marked | ||
| as important (lines 4 to 8). All rules are evaluated. |
Co-authored-by: Tom Schraitle <[email protected]>
Co-authored-by: Tom Schraitle <[email protected]>
Co-authored-by: Tom Schraitle <[email protected]>
Co-authored-by: Tom Schraitle <[email protected]>
Co-authored-by: Tom Schraitle <[email protected]>
42dab29 to
00dfa20
Compare
This is the second article from the series that aims to merge and update the content about Snapper from the Admin Guide.