10
New Version of Bonsai to help you managing your OS deployments is out (discuss.tchncs.de)
submitted 4 months ago by to c/gnome@discuss.tchncs.de
11 comments fedilink hide all child comments
 

A new version of Bonsai is out!

You can do now the following things:

  • View your deployments details (Layered, removed and replaced for remote and local packages)
  • Pin and unpin deployments
  • Set a deployment to be booted next
  • Delete a deployment
  • Rebase to an other branch
  • Add new remote branches
  • See pending changes
  • Add layered/remove packages
  • Delete overwrites (remove layered packages, restore removed base packages)

It is also now available via Flatpak:

flatpak install https://codeberg.org/petsoi/bonsai/raw/branch/main/page.codeberg.petsoi.bonsai.flatpakref

Have fun using it! Feedback is welcome!

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 4 months ago* (last edited 4 months ago) (7 children)

I'm not sure how much advantages a preview option for downloading would have. After having done the regular download, one sees the not yet started image (with the ⏳ next to it), then you can inspect and delete it, if you want. Or is there some more things you could do with preview?

Thanks for the feedback. When you do the + and select branch, a rebase button appears, When you press that, it will rebase. There is currently no fetch option.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 1 point 4 months ago (6 children)

    lol I forgot we can inspect the deployment after that, I just think that it feels a little harsh to just press “update” blindly without knowing anything about the download, rpm-partee update —check also exists to avoid redundancies

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] [S] 1 point 4 months ago (5 children)

    Do you mean rpm-ostree upgrade --preview?

    Hmm I wonder how a nice UI could look like...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 4 months ago* (4 children)

    hi, what I meant was…

    you told me that update —preview would be redundant if we can check the deployment anyways after the update

    in that case, we can instead see update —check as a brief summary and also as a way to ask for confirmation, it wouldn’t need that much space to display

    btw nice to see you here, I don’t have Github or Reddit accounts to give feedback on there :)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S] 2 points 4 months ago* (last edited 4 months ago)

    Btw, I think, I have a good idea, how to display the content of --preview, UI wise. On my machine it takes approximately as long as --check. So I could use it, instead of preview and then display the upcoming changes with the + Button (which could have a integrated drop down.)

    I need to check, how much complexity that adds, or if there is a clever way to implement that.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 1 point 4 months ago

    So the + button shows up if update --check returns that there is something to update. But I'm not sure what additional info it provides which is worth displaying.

    What do you think of?

    Btw. it's not on Github, but on Codeberg.org 😀️

  • permalink
  • fedilink
  • source
  • parent