Skip to content
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

xst is behind st. Is this project still maintained? #142

Closed
pfr-dev opened this issue Mar 15, 2022 · 5 comments · Fixed by #143
Closed

xst is behind st. Is this project still maintained? #142

pfr-dev opened this issue Mar 15, 2022 · 5 comments · Fixed by #143

Comments

@pfr-dev
Copy link

pfr-dev commented Mar 15, 2022

Just wondering if xst is still maintained as st has been at v0.8.5 since early Jan and xst is still on v0.8.4 and hasn't been updated for over 18 months.

Cheers

@carlitos777
Copy link

+1

@neeasade
Copy link
Member

neeasade commented Mar 15, 2022

is this project still maintained

yes-ish. I check upstream every 6 months or so

Thanks for the bump, all that has to happen is a git pull git://git.suckless.org/st + conflict resolution (and then some light testing). This will happen when the stars align ⭐ 🌟 .

edit:

and hasn't been updated for over 18 months.

The last commit was 59 days ago.

@neeasade neeasade mentioned this issue Mar 15, 2022
3 tasks
@pfr-dev
Copy link
Author

pfr-dev commented Mar 28, 2022

Cool thanks! I only ask because the xst package on NetBSD is maintained by pin who tends to drop packages if they're not regularly updated. I think he needs regular releases in order to update the package in pkgsrc. I only bumped this thread because I use xst on my NetBSD machine and didn't want it to get dropped from his 'portfolio' :)

As such, can we get a new release tag please 👍

@0323pin
Copy link

0323pin commented Mar 28, 2022

xst package on NetBSD is maintained by pin who tends to drop packages if they're not regularly updated.

This has been updated now and when a new release becomes available, the package will be updated.

I think he needs regular releases in order to update the package in pkgsrc

I try to avoid git-HEAD builds in the main branch, yes. But, it's up to upstream to judge when they want to tag a new release or not.

@neeasade
Copy link
Member

Tracking thoughts/path to a 0.8.5 tag here for transparency: #145. I have some time off through the next week, so this will likely get some love.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants