* [ISSUE] Package request: Update existing libspnav to 1.1
@ 2023-06-21 14:20 CtrlC-Root
2023-06-21 16:29 ` classabbyamp
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: CtrlC-Root @ 2023-06-21 14:20 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
New issue by CtrlC-Root on void-packages repository
https://github.com/void-linux/void-packages/issues/44550
Description:
### Package name
libspnav
### Package homepage
https://github.com/FreeSpacenav/libspnav
### Description
I want to make PRs to package [spacenavd](https://github.com/FreeSpacenav/spacenavd) and [spnavcfg](https://github.com/FreeSpacenav/spnavcfg). These depend on [libspnav](https://github.com/FreeSpacenav/libspnav) which is [currently packaged](https://github.com/void-linux/void-packages/blob/master/srcpkgs/libspnav/template) but out of date. Some updates on the package:
* The releases are now available on GitHub (see links above).
* The new version supports a non-X11 build as well as the X11 build. It would be nice to have both as variants although I'm not familiar enough with XBPS to know if this is possible or how it would work.
Heads up @yopito since you are the current maintainer and was the last one to update the libspnav package.
Also linking a previous PR to package spacenavd at https://github.com/void-linux/void-packages/pull/19269 which seems to have been closed for some reason.
### Does the requested package meet the package requirements?
Compiled, Required
### Is the requested package released?
Yes
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Package request: Update existing libspnav to 1.1
2023-06-21 14:20 [ISSUE] Package request: Update existing libspnav to 1.1 CtrlC-Root
@ 2023-06-21 16:29 ` classabbyamp
2023-06-21 16:29 ` [ISSUE] [CLOSED] " classabbyamp
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: classabbyamp @ 2023-06-21 16:29 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/44550#issuecomment-1601158759
Comment:
> Don't request an update of a package, We have a script for that: https://repo-default.voidlinux.org/void-updates/void-updates.txt
> However, a quality pull request may help.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [ISSUE] [CLOSED] Package request: Update existing libspnav to 1.1
2023-06-21 14:20 [ISSUE] Package request: Update existing libspnav to 1.1 CtrlC-Root
2023-06-21 16:29 ` classabbyamp
@ 2023-06-21 16:29 ` classabbyamp
2023-06-21 16:47 ` CtrlC-Root
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: classabbyamp @ 2023-06-21 16:29 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
Closed issue by CtrlC-Root on void-packages repository
https://github.com/void-linux/void-packages/issues/44550
Description:
### Package name
libspnav
### Package homepage
https://github.com/FreeSpacenav/libspnav
### Description
I want to make PRs to package [spacenavd](https://github.com/FreeSpacenav/spacenavd) and [spnavcfg](https://github.com/FreeSpacenav/spnavcfg). These depend on [libspnav](https://github.com/FreeSpacenav/libspnav) which is [currently packaged](https://github.com/void-linux/void-packages/blob/master/srcpkgs/libspnav/template) but out of date. Some updates on the package:
* The releases are now available on GitHub (see links above).
* The new version supports a non-X11 build as well as the X11 build. It would be nice to have both as variants although I'm not familiar enough with XBPS to know if this is possible or how it would work.
Heads up @yopito since you are the current maintainer and was the last one to update the libspnav package.
Also linking a previous PR to package spacenavd at https://github.com/void-linux/void-packages/pull/19269 which seems to have been closed for some reason.
### Does the requested package meet the package requirements?
Compiled, Required
### Is the requested package released?
Yes
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Package request: Update existing libspnav to 1.1
2023-06-21 14:20 [ISSUE] Package request: Update existing libspnav to 1.1 CtrlC-Root
2023-06-21 16:29 ` classabbyamp
2023-06-21 16:29 ` [ISSUE] [CLOSED] " classabbyamp
@ 2023-06-21 16:47 ` CtrlC-Root
2023-06-21 16:58 ` CtrlC-Root
2023-07-13 18:34 ` CtrlC-Root
4 siblings, 0 replies; 6+ messages in thread
From: CtrlC-Root @ 2023-06-21 16:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
New comment by CtrlC-Root on void-packages repository
https://github.com/void-linux/void-packages/issues/44550#issuecomment-1601204609
Comment:
I see that but it's not clear to me what to do when the change is more than updating to a new version. Did I miss some part of the documentation that talks about the process for this? Specifically:
> * The releases are now available on GitHub (see links above).
And Sourceforge no longer has the newer release. So it's not just a package version update.
> * The new version supports a non-X11 build as well as the X11 build. It would be nice to have both as variants although I'm not familiar enough with XBPS to know if this is possible or how it would work.
Should these be separate packages? How does this work in XBPS?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Package request: Update existing libspnav to 1.1
2023-06-21 14:20 [ISSUE] Package request: Update existing libspnav to 1.1 CtrlC-Root
` (2 preceding siblings ...)
2023-06-21 16:47 ` CtrlC-Root
@ 2023-06-21 16:58 ` CtrlC-Root
2023-07-13 18:34 ` CtrlC-Root
4 siblings, 0 replies; 6+ messages in thread
From: CtrlC-Root @ 2023-06-21 16:58 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
New comment by CtrlC-Root on void-packages repository
https://github.com/void-linux/void-packages/issues/44550#issuecomment-1601233343
Comment:
To clarify, given FreeCAD builds on top of libspnav, updating the library and packaging the necessary tools to actually use the functionality will likely require 3+ PRs. That could take weeks (https://github.com/void-linux/void-packages/pull/44235). That is a lot of work to do with no discussion, guidance, or expectation of it being accepted beforehand. What is the appropriate process to engage with the community around this kind of work before starting on it?
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Package request: Update existing libspnav to 1.1
2023-06-21 14:20 [ISSUE] Package request: Update existing libspnav to 1.1 CtrlC-Root
` (3 preceding siblings ...)
2023-06-21 16:58 ` CtrlC-Root
@ 2023-07-13 18:34 ` CtrlC-Root
4 siblings, 0 replies; 6+ messages in thread
From: CtrlC-Root @ 2023-07-13 18:34 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
New comment by CtrlC-Root on void-packages repository
https://github.com/void-linux/void-packages/issues/44550#issuecomment-1601233343
Comment:
To clarify, given FreeCAD builds on top of libspnav, updating the library and packaging the necessary tools to actually use the functionality will likely require 3+ PRs. That could take weeks (https://github.com/void-linux/void-packages/pull/44235). That is a lot of work to do with no discussion, guidance, or expectation of it being accepted beforehand. What is the appropriate process to engage with the community around this kind of work before starting on it?
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-07-13 18:34 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-21 14:20 [ISSUE] Package request: Update existing libspnav to 1.1 CtrlC-Root
2023-06-21 16:29 ` classabbyamp
2023-06-21 16:29 ` [ISSUE] [CLOSED] " classabbyamp
2023-06-21 16:47 ` CtrlC-Root
2023-06-21 16:58 ` CtrlC-Root
2023-07-13 18:34 ` CtrlC-Root
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).