-
Notifications
You must be signed in to change notification settings - Fork 184
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
Add a section pointing to package development #754
Comments
Good idea. My connecting point would be "Virtual Packages" (in 4.1 Advanced Usage) and xbps-create (not listed). I am not at all against a whole page. But the handbook should at least mention/link this. This issue seems related to (old) #616 which I try to revive. |
I don't think this is a good idea, we have MANUAL.md and CONTRIBUTING.md in the void-packages repository and this would be just duplicating that information. (also, xbps-create shouldn't really be used outside of xbps-src) |
It is not a duplication when you just mention/link it for completeness sake. I thought xbps-create could be used to kind of extend the virtualpkg= functionality. Another open issue 631 has problems with the example itself (virtualpkg=linux:linux5.6). Anyway you look at it, there are loose ends: I can go "There is also That is all it takes. Otherwise I feel like "Function defined but not called". My main point is that it is all about xbps-commands and the design of 4. XBPS Package Manager part. |
Oh well, I just saw it already is there, the link to void-packages README.md! Between xbps.d link and "Updating". "To learn how to build packages from source..." xbps-src is mentioned in other places in the handbook, but not here. No problem, but that could explain my slight confusion. |
Before opening a request, please be sure to check what content is suitable for the Handbook.
I've read it and still think it would be nice to have.
We prioritise requests for information specific to Void, and try to avoid duplicating information already available elsewhere (e.g. on the Arch wiki).
This is void-specific.
It would be nice to have some pointers related to packaging.
I looked at:
The site or doc could have some links pointing to:
WDYT ?
If this is acceptable, I can craft a PR.
The text was updated successfully, but these errors were encountered: