* [ISSUE] Making a devel subpackage: File conflicts
@ 2020-11-18 6:10 harrisonthorne
2020-11-18 8:10 ` st3r4g
` (6 more replies)
0 siblings, 7 replies; 8+ messages in thread
From: harrisonthorne @ 2020-11-18 6:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1814 bytes --]
New issue by harrisonthorne on void-packages repository
https://github.com/void-linux/void-packages/issues/26474
Description:
I'm still learning how to make Void packages. It's been a super pleasant experience, though.
I'm making a package for `tree-sitter`, which seems to be a dependency of Neovim's upcoming 0.5 release.
template:
```
# Template file for 'tree-sitter'
pkgname=tree-sitter
version=0.17.3
revision=1
build_style=gnu-makefile
short_desc="Parser generator tool and incremental parsing library"
maintainer="Harrison Thorne <harrisonthorne@protonmail.com>"
license="MIT"
homepage="https://tree-sitter.github.io"
distfiles="https://github.com/tree-sitter/${pkgname}/archive/${version}.tar.gz"
checksum=a897e5c9a7ccb74271d9b20d59121d2d2e9de8b896c4d1cfaac0f8104c1ef9f8
tree-sitter-devel_package() {
short_desc+=" - development files"
depends="${sourcepkg}>=${version}_${revision}"
pkg_install() {
vmove usr/include
vmove "usr/lib/*.a"
vmove "usr/lib/*.so"
vmove usr/lib/pkgconfig
}
}
```
Then, when I add `tree-sitter-devel` to `neovim`'s `makedepends`, I get this with `xbps-src pkg neovim`:
```
ERROR: tree-sitter-devel-0.17.3_1: file `/usr/include/tree_sitter/api.h' already installed by package tree-sitter-0.17.3_1.
ERROR: tree-sitter-devel-0.17.3_1: file `/usr/include/tree_sitter/parser.h' already installed by package tree-sitter-0.17.3_1.
ERROR: tree-sitter-devel-0.17.3_1: file `/usr/lib/libtree-sitter.a' already installed by package tree-sitter-0.17.3_1.
ERROR: tree-sitter-devel-0.17.3_1: file `/usr/lib/pkgconfig/tree-sitter.pc' already installed by package tree-sitter-0.17.3_1.
ERROR: tree-sitter-devel-0.17.3_1: file `/usr/lib/libtree-sitter.so' already installed by package tree-sitter-0.17.3_1.
```
Why is this happening?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Making a devel subpackage: File conflicts
2020-11-18 6:10 [ISSUE] Making a devel subpackage: File conflicts harrisonthorne
@ 2020-11-18 8:10 ` st3r4g
2020-11-18 8:11 ` st3r4g
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: st3r4g @ 2020-11-18 8:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/26474#issuecomment-729510983
Comment:
It seems that your `tree-sitter` and `tree-sitter-devel` binary packages contain the same files. Maybe you added the `-devel` subpackage after the first was already created or something like that. I would start again from a clean state:
```
./xbps-src clean tree-sitter
./xbps-src -f pkg tree-sitter
```
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Making a devel subpackage: File conflicts
2020-11-18 6:10 [ISSUE] Making a devel subpackage: File conflicts harrisonthorne
2020-11-18 8:10 ` st3r4g
@ 2020-11-18 8:11 ` st3r4g
2020-11-18 8:11 ` st3r4g
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: st3r4g @ 2020-11-18 8:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/26474#issuecomment-729510983
Comment:
It seems that your `tree-sitter` and `tree-sitter-devel` binary packages contain some identical files. Maybe you added the `-devel` subpackage after the first was already created or something like that. I would start again from a clean state:
```
./xbps-src clean tree-sitter
./xbps-src -f pkg tree-sitter
```
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Making a devel subpackage: File conflicts
2020-11-18 6:10 [ISSUE] Making a devel subpackage: File conflicts harrisonthorne
2020-11-18 8:10 ` st3r4g
2020-11-18 8:11 ` st3r4g
@ 2020-11-18 8:11 ` st3r4g
2020-11-18 8:15 ` st3r4g
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: st3r4g @ 2020-11-18 8:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/26474#issuecomment-729510983
Comment:
It seems that your `tree-sitter` and `tree-sitter-devel` binary packages contain some identical files. Maybe you added the `devel` subpackage after the first was already created or something like that. I would start again from a clean state:
```
./xbps-src clean tree-sitter
./xbps-src -f pkg tree-sitter
```
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Making a devel subpackage: File conflicts
2020-11-18 6:10 [ISSUE] Making a devel subpackage: File conflicts harrisonthorne
` (2 preceding siblings ...)
2020-11-18 8:11 ` st3r4g
@ 2020-11-18 8:15 ` st3r4g
2020-11-18 8:15 ` st3r4g
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: st3r4g @ 2020-11-18 8:15 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/26474#issuecomment-729510983
Comment:
It seems that your `tree-sitter` and `tree-sitter-devel` binary packages contain some identical files. Maybe you added the `devel` subpackage after the first was already created or something like that. I would start again from a clean state:
```
./xbps-src clean tree-sitter
./xbps-src -f pkg tree-sitter
```
Note: you can show the contents of a built package with `xls <name>`
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Making a devel subpackage: File conflicts
2020-11-18 6:10 [ISSUE] Making a devel subpackage: File conflicts harrisonthorne
` (3 preceding siblings ...)
2020-11-18 8:15 ` st3r4g
@ 2020-11-18 8:15 ` st3r4g
2020-11-18 14:41 ` [ISSUE] [CLOSED] " harrisonthorne
2020-11-18 14:41 ` harrisonthorne
6 siblings, 0 replies; 8+ messages in thread
From: st3r4g @ 2020-11-18 8:15 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/26474#issuecomment-729510983
Comment:
It seems that your `tree-sitter` and `tree-sitter-devel` binary packages contain some identical files. Maybe you added the `devel` subpackage after the first was already created or something like that. I would start again from a clean state:
```
./xbps-src clean tree-sitter
./xbps-src -f pkg tree-sitter
```
Note: you can see the contents of a built package with `xls <name>`
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Making a devel subpackage: File conflicts
2020-11-18 6:10 [ISSUE] Making a devel subpackage: File conflicts harrisonthorne
` (5 preceding siblings ...)
2020-11-18 14:41 ` [ISSUE] [CLOSED] " harrisonthorne
@ 2020-11-18 14:41 ` harrisonthorne
6 siblings, 0 replies; 8+ messages in thread
From: harrisonthorne @ 2020-11-18 14:41 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
New comment by harrisonthorne on void-packages repository
https://github.com/void-linux/void-packages/issues/26474#issuecomment-729723572
Comment:
Thank you! The `-f` flag was the trick :P
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [ISSUE] [CLOSED] Making a devel subpackage: File conflicts
2020-11-18 6:10 [ISSUE] Making a devel subpackage: File conflicts harrisonthorne
` (4 preceding siblings ...)
2020-11-18 8:15 ` st3r4g
@ 2020-11-18 14:41 ` harrisonthorne
2020-11-18 14:41 ` harrisonthorne
6 siblings, 0 replies; 8+ messages in thread
From: harrisonthorne @ 2020-11-18 14:41 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]
Closed issue by harrisonthorne on void-packages repository
https://github.com/void-linux/void-packages/issues/26474
Description:
I'm still learning how to make Void packages. It's been a super pleasant experience, though.
I'm making a package for `tree-sitter`, which seems to be a dependency of Neovim's upcoming 0.5 release.
template:
```
# Template file for 'tree-sitter'
pkgname=tree-sitter
version=0.17.3
revision=1
build_style=gnu-makefile
short_desc="Parser generator tool and incremental parsing library"
maintainer="Harrison Thorne <harrisonthorne@protonmail.com>"
license="MIT"
homepage="https://tree-sitter.github.io"
distfiles="https://github.com/tree-sitter/${pkgname}/archive/${version}.tar.gz"
checksum=a897e5c9a7ccb74271d9b20d59121d2d2e9de8b896c4d1cfaac0f8104c1ef9f8
tree-sitter-devel_package() {
short_desc+=" - development files"
depends="${sourcepkg}>=${version}_${revision}"
pkg_install() {
vmove usr/include
vmove "usr/lib/*.a"
vmove "usr/lib/*.so"
vmove usr/lib/pkgconfig
}
}
```
Then, when I add `tree-sitter-devel` to `neovim`'s `makedepends`, I get this with `xbps-src pkg neovim`:
```
ERROR: tree-sitter-devel-0.17.3_1: file `/usr/include/tree_sitter/api.h' already installed by package tree-sitter-0.17.3_1.
ERROR: tree-sitter-devel-0.17.3_1: file `/usr/include/tree_sitter/parser.h' already installed by package tree-sitter-0.17.3_1.
ERROR: tree-sitter-devel-0.17.3_1: file `/usr/lib/libtree-sitter.a' already installed by package tree-sitter-0.17.3_1.
ERROR: tree-sitter-devel-0.17.3_1: file `/usr/lib/pkgconfig/tree-sitter.pc' already installed by package tree-sitter-0.17.3_1.
ERROR: tree-sitter-devel-0.17.3_1: file `/usr/lib/libtree-sitter.so' already installed by package tree-sitter-0.17.3_1.
```
Why is this happening?
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2020-11-18 14:41 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-18 6:10 [ISSUE] Making a devel subpackage: File conflicts harrisonthorne
2020-11-18 8:10 ` st3r4g
2020-11-18 8:11 ` st3r4g
2020-11-18 8:11 ` st3r4g
2020-11-18 8:15 ` st3r4g
2020-11-18 8:15 ` st3r4g
2020-11-18 14:41 ` [ISSUE] [CLOSED] " harrisonthorne
2020-11-18 14:41 ` harrisonthorne
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).