* Re: Package request: tre
2023-11-24 23:16 [ISSUE] Package request: tre LinArcX
@ 2023-12-04 13:37 ` realcharmer
2023-12-04 13:45 ` LinArcX
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: realcharmer @ 2023-12-04 13:37 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
New comment by realcharmer on void-packages repository
https://github.com/void-linux/void-packages/issues/47380#issuecomment-1838660351
Comment:
The `tre` package name is taken in https://github.com/void-linux/void-packages/blob/master/srcpkgs/tre/template. What do you suggest the name should be?
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Package request: tre
2023-11-24 23:16 [ISSUE] Package request: tre LinArcX
2023-12-04 13:37 ` realcharmer
@ 2023-12-04 13:45 ` LinArcX
2023-12-04 13:53 ` realcharmer
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: LinArcX @ 2023-12-04 13:45 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
New comment by LinArcX on void-packages repository
https://github.com/void-linux/void-packages/issues/47380#issuecomment-1838674733
Comment:
sigh!
maybe:
- 3(i don't know if a number can be a name of a package. but it's super minimal and convenient to type regularly)
- rename the previous package as 'tre-lib' and keep this new package as 'tre'.
- 3re
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Package request: tre
2023-11-24 23:16 [ISSUE] Package request: tre LinArcX
2023-12-04 13:37 ` realcharmer
2023-12-04 13:45 ` LinArcX
@ 2023-12-04 13:53 ` realcharmer
2023-12-04 14:07 ` LinArcX
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: realcharmer @ 2023-12-04 13:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
New comment by realcharmer on void-packages repository
https://github.com/void-linux/void-packages/issues/47380#issuecomment-1838688333
Comment:
The original `tre` package upstream seems abandoned. The question is whether we want to keep it. This is a question for the maintainers though. I am willing to write and maintain the new package after this naming issue is resolved.
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Package request: tre
2023-11-24 23:16 [ISSUE] Package request: tre LinArcX
` (2 preceding siblings ...)
2023-12-04 13:53 ` realcharmer
@ 2023-12-04 14:07 ` LinArcX
2023-12-04 16:00 ` leahneukirchen
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: LinArcX @ 2023-12-04 14:07 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 283 bytes --]
New comment by LinArcX on void-packages repository
https://github.com/void-linux/void-packages/issues/47380#issuecomment-1838712437
Comment:
I guess there are some policiese regarding to maintain outdated packages in void. Still not sure.
maybe @Duncaen or @pullmoll can help us.
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Package request: tre
2023-11-24 23:16 [ISSUE] Package request: tre LinArcX
` (3 preceding siblings ...)
2023-12-04 14:07 ` LinArcX
@ 2023-12-04 16:00 ` leahneukirchen
2023-12-04 16:07 ` Duncaen
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: leahneukirchen @ 2023-12-04 16:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
New comment by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/47380#issuecomment-1838951770
Comment:
Two packages use tre-devel, so we can't drop that.
But you can rename this to tre-rust or something.
Or rename tre to libtre.
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Package request: tre
2023-11-24 23:16 [ISSUE] Package request: tre LinArcX
` (4 preceding siblings ...)
2023-12-04 16:00 ` leahneukirchen
@ 2023-12-04 16:07 ` Duncaen
2023-12-04 17:08 ` leahneukirchen
2023-12-05 21:39 ` CameronNemo
7 siblings, 0 replies; 9+ messages in thread
From: Duncaen @ 2023-12-04 16:07 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/47380#issuecomment-1838965639
Comment:
`tre` also has `agrep` so some people might have installed it manually, if this wasn't the case and it was just a library I would rename it.
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Package request: tre
2023-11-24 23:16 [ISSUE] Package request: tre LinArcX
` (5 preceding siblings ...)
2023-12-04 16:07 ` Duncaen
@ 2023-12-04 17:08 ` leahneukirchen
2023-12-05 21:39 ` CameronNemo
7 siblings, 0 replies; 9+ messages in thread
From: leahneukirchen @ 2023-12-04 17:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 241 bytes --]
New comment by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/47380#issuecomment-1839095337
Comment:
Moving tre to libtre and making agrep a subpackage agrep would probably improve things. :)
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Package request: tre
2023-11-24 23:16 [ISSUE] Package request: tre LinArcX
` (6 preceding siblings ...)
2023-12-04 17:08 ` leahneukirchen
@ 2023-12-05 21:39 ` CameronNemo
7 siblings, 0 replies; 9+ messages in thread
From: CameronNemo @ 2023-12-05 21:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
New comment by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/issues/47380#issuecomment-1841657383
Comment:
Hmm perhaps lsd fits your needs? The latest tre commit and release appears to be over a year old. (not sure how important that is)
https://github.com/dduan/tre/issues/135
^ permalink raw reply [flat|nested] 9+ messages in thread