Skip to content

Commit

Permalink
Update date
Browse files Browse the repository at this point in the history
  • Loading branch information
@jarun
jarun committed Jan 9, 2018
1 parent 9681216 commit 454b136
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion CHANGELOG
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
Buku 3.6
2018-01-06
2018-01-09

What's in?
- Skip bookmark addition if edit is aborted
Expand Down
2 changes: 1 addition & 1 deletion buku.1
View file
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
.TH "BUKU" "1" "06 Jan 2018" "Version 3.6" "User Commands"
.TH "BUKU" "1" "09 Jan 2018" "Version 3.6" "User Commands"
.SH NAME
buku \- Powerful command-line bookmark manager.
.SH SYNOPSIS
Expand Down

10 comments on commit 454b136

@jarun
Copy link
Owner Author

@jarun jarun commented on 454b136 Jan 9, 2018 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shaggytwodope is there any alternative (and more reliable) packaging system to packagecore you know of? I keep trying to make releases and keep wasting time because of recurring issues. The turnaround time for the fixes is reasonably high. If there's a better alternative that's equally simple to setup, I will abandon it gladly.

@dilawar what is the learning curve/effort required to move to SUSE's build system? If feasible, I would consider moving the packaging of all my projects there.

@jarun
Copy link
Owner Author

@jarun jarun commented on 454b136 Jan 9, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shaggytwodope @szlin @zmwangx Buku v3.6 is released!

@dilawar
Copy link

@dilawar dilawar commented on 454b136 Jan 9, 2018 •
edited by jarun
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you are comfortable with writing spec file then probably not very much. Slightly more work for packaging for debian/ububtu (see the link at the bottom where they explain howto). Once setup, then not much work in maintainence.

Good part: You can install their open build service (obs) locally (I use Ububntu-14.04) and test your package. obs downloads the environement locally (fedora, SUSE etc.) and build using chroot. So packages created are robust. Once local build is successful, you can commit to the build service repo. Here is your nnn package which I am building on obs in my personal repo: https://build.opensuse.org/package/show/home:dilawar/nnn

This service is very robust. I've never had any issue with it. The documentation is just enough: https://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto .

@jarun
Copy link
Owner Author

@jarun jarun commented on 454b136 Jan 9, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've never worked with a spec file myself, not sure about @shaggytwodope. I see that you are using cmake. So are you also having any additional local files?

I see you build for CentOS 7 and Fedora 26. How about the latest releases like CentOS 7.3 and Fedora 27. How quickly after release does obs start supporting those?

@szlin
Copy link
Collaborator

@szlin szlin commented on 454b136 Jan 9, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jarun The new version of buku has been uploaded. Thanks.

@jarun
Copy link
Owner Author

@jarun jarun commented on 454b136 Jan 9, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @szlin! Can you also review jarun/nnn#76?

@dilawar
Copy link

@dilawar dilawar commented on 454b136 Jan 10, 2018 via email

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jarun
Copy link
Owner Author

@jarun jarun commented on 454b136 Jan 10, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the details. One of the reasons behind going with PackageCore is they are quick to pick new releases. I got a response from the chief maintainer today that they have resolved both the issues (though we have already released Buku v3.6) I raised.

As for Buku, I think we are pretty much done with development and the project is stable enough. I'm not expecting a new release within next 4/5 months.

The next time I plan a new release for any of my other tools I will evaluate how PackageCore is doing and probably take a call on the spot. As I understand, the changes might take a day or two and we might need your valuable help with it.

@dilawar
Copy link

@dilawar dilawar commented on 454b136 Jan 11, 2018 via email

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jarun
Copy link
Owner Author

@jarun jarun commented on 454b136 Jan 11, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I second that. A single system with all the goodies is the only right approach. On Ubuntu I do miss the differential updates on openSUSE.

Please sign in to comment.