Article Summary: More recently in version 2023.06 of rpm-ostree a search command has been added:
rpm-ostree now supports the “search” verb allowing users to use rpm-ostree to search for available packages. An example of this is: rpm-ostree search *kernel
It’s very unlikely that users read the rpm-ostree changelog, so an article about the new feature should allow them to know that the feature now exists.
Article Description: The idea of the article would be mostly to show the old way users of ostree-based distros had to search for packages (that is, with dnf from inside a toolbox) and afterwards present an example of the new way with a search for neofetch using rpm-ostree search neofetch.
rpm-ostree search neofetch
Metadata Update from @rlengland: - Issue assigned to mateusrodcosta - Issue tagged with: article, needs-image
I wrote my first draft: https://fedoramagazine.org/wp-admin/post.php?post=39066&action=edit
I didn't know how to do the quote from the Github release, so any feedback is appreciated.
Metadata Update from @rlengland: - Custom field preview-link adjusted to https://fedoramagazine.org/?p=39066&preview=true&preview_id=39066
Any updates on this?
Sorry @mateusrodcosta we'll take a look at it tomorrow and get back to you. No excuse on our part, just slippped up getting to it.
Tweaked a few lines but LGTM. Thanks!
Metadata Update from @rlengland: - Custom field editor adjusted to rlengland - Custom field image-editor adjusted to rlengland
@mateusrodcosta I've edited your article to perhaps clarify/simplify some locations but I've tried to be true to your original. If you can take a few minutes to review it to insure I've not changed your meaning that would be helpful.
I will be working on a feature image, probably something based on a magnifying glass. If you have suggestions let us know.
I will hopefully target this for Wednesday (29 Nov).
Looks good, though there's is a small issue with spaces in the second paragraph.
I did notice that the quote from the changelog about the search verb has been removed, that is probably ok.
Just to confirm, would it make sense to have a Conclusion for this article? I didn't initially write one because I was unsure of what to write, but I could try to come up with something if you guys say it makes sense to have one.
Thanks for catching the spacing issue.
My thought on the changelog quote was that it was probably just as good to refer the reader (via a link) to the release notes. This somewhat simplified the appearance.
If you have something to add as a Conclusion section then by all means add it. But the article has done what it intended to do with out it. Sometimes simple is good. :-)
Metadata Update from @rlengland: - Custom field publish adjusted to 2023-11-29
Metadata Update from @rlengland: - Issue untagged with: needs-image
Seems I accidentally left in the prompt on the last example, I will edit it out.
Edit: Seems I can't edit, could someone change [mateusrc@fedora ~]$ rpm-ostree search neofetch to $ rpm-ostree search neofetch on the last example?
[mateusrc@fedora ~]$ rpm-ostree search neofetch
$ rpm-ostree search neofetch
@mateusrodcosta Done. FYI After publication it takes an editor to make updates.
Issue status updated to: Closed (was: Open) Issue close_status updated to: published