* Re: binutils: remove dependency to binutils-doc
2021-05-04 18:16 [PR PATCH] binutils: remove dependency to binutils-doc ailiop-git
@ 2021-05-04 18:18 ` ericonr
2021-05-04 18:19 ` ericonr
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: ericonr @ 2021-05-04 18:18 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30678#issuecomment-832146163
Comment:
binutils is 26MB, binutils-doc is less than 1MB. IMO it makes more sense to remove the subpackage completely and fold it into `binutils` (add replaces="binutils-doc>=0"` to `binutils`).
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: binutils: remove dependency to binutils-doc
2021-05-04 18:16 [PR PATCH] binutils: remove dependency to binutils-doc ailiop-git
2021-05-04 18:18 ` ericonr
@ 2021-05-04 18:19 ` ericonr
2021-05-04 18:24 ` ericonr
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: ericonr @ 2021-05-04 18:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30678#issuecomment-832146163
Comment:
binutils is 26MB, binutils-doc is less than 1MB. IMO it makes more sense to remove the subpackage completely and fold it into `binutils` (add `replaces="binutils-doc>=0"` to `binutils`).
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: binutils: remove dependency to binutils-doc
2021-05-04 18:16 [PR PATCH] binutils: remove dependency to binutils-doc ailiop-git
2021-05-04 18:18 ` ericonr
2021-05-04 18:19 ` ericonr
@ 2021-05-04 18:24 ` ericonr
2021-05-04 18:46 ` ailiop-git
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: ericonr @ 2021-05-04 18:24 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30678#issuecomment-832150009
Comment:
Ah, it isn't explained properly. It's split off because other packages depend on it: `xbps-query -RX binutils-doc`.
You could add a comment about it to the template instead, maybe.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: binutils: remove dependency to binutils-doc
2021-05-04 18:16 [PR PATCH] binutils: remove dependency to binutils-doc ailiop-git
` (2 preceding siblings ...)
2021-05-04 18:24 ` ericonr
@ 2021-05-04 18:46 ` ailiop-git
2021-05-04 19:32 ` ericonr
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: ailiop-git @ 2021-05-04 18:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/30678#issuecomment-832163568
Comment:
So I agree with folding it into the main package, if we are to follow the manual guideline given that the size of the docs is the deciding factor (we do have other packages with tiny docs split off into a subpkg, e.g. 66, which probably need fixing).
I'm assuming that the original reason was so that the cross binutils can share the doc, but they certainly don't depend on it (so we probably better remove the depends from them). Both cross-arm-none-eabi-binutils and cross-or1k-none-elf-binutils rm the info files at the post_install phase so there should be no conflict.
What do you think?
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: binutils: remove dependency to binutils-doc
2021-05-04 18:16 [PR PATCH] binutils: remove dependency to binutils-doc ailiop-git
` (3 preceding siblings ...)
2021-05-04 18:46 ` ailiop-git
@ 2021-05-04 19:32 ` ericonr
2021-05-04 19:33 ` ericonr
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: ericonr @ 2021-05-04 19:32 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30678#issuecomment-832190687
Comment:
The idea of the split is that it becomes necessary because we have many `binutils` packages which would otherwise conflict. But `docs` as a split package solve this. In that way, the fact that it's a subpackage could be considered an implementation detail (in order for all the packages to provide the complete deal, including docs) rather than something users should be worrying about, so I would go as far as to say there is nothing to change.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: binutils: remove dependency to binutils-doc
2021-05-04 18:16 [PR PATCH] binutils: remove dependency to binutils-doc ailiop-git
` (4 preceding siblings ...)
2021-05-04 19:32 ` ericonr
@ 2021-05-04 19:33 ` ericonr
2022-05-19 2:16 ` github-actions
2022-06-03 2:11 ` [PR PATCH] [Closed]: " github-actions
7 siblings, 0 replies; 9+ messages in thread
From: ericonr @ 2021-05-04 19:33 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/30678#issuecomment-832190953
Comment:
People consciously added `binutils-doc` to depends for the other packages, so I expect there to have been actual demand.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: binutils: remove dependency to binutils-doc
2021-05-04 18:16 [PR PATCH] binutils: remove dependency to binutils-doc ailiop-git
` (5 preceding siblings ...)
2021-05-04 19:33 ` ericonr
@ 2022-05-19 2:16 ` github-actions
2022-06-03 2:11 ` [PR PATCH] [Closed]: " github-actions
7 siblings, 0 replies; 9+ messages in thread
From: github-actions @ 2022-05-19 2:16 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/pull/30678#issuecomment-1131014221
Comment:
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PR PATCH] [Closed]: binutils: remove dependency to binutils-doc
2021-05-04 18:16 [PR PATCH] binutils: remove dependency to binutils-doc ailiop-git
` (6 preceding siblings ...)
2022-05-19 2:16 ` github-actions
@ 2022-06-03 2:11 ` github-actions
7 siblings, 0 replies; 9+ messages in thread
From: github-actions @ 2022-06-03 2:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]
There's a closed pull request on the void-packages repository
binutils: remove dependency to binutils-doc
https://github.com/void-linux/void-packages/pull/30678
Description:
The binutils main package doesn't depend on the info files contained in
the documentation package. Remove it from being a dependency similar to
any other package whose documentation is split off into a subpackage.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
^ permalink raw reply [flat|nested] 9+ messages in thread