Michael wrote:
> On Thursday 19 December 2024 20:47:57 GMT Dale wrote:
>> Michael wrote:
>>> On Thursday 19 December 2024 18:02:29 GMT Matt Connell wrote:
On Thu, 2024-12-19 at 11:57 -0600, Dale wrote:
> Some, llvm for example, has a "*" included.
Almost certain this is because the p
On Thursday 19 December 2024 20:47:57 GMT Dale wrote:
> Michael wrote:
> > On Thursday 19 December 2024 18:02:29 GMT Matt Connell wrote:
> >> On Thu, 2024-12-19 at 11:57 -0600, Dale wrote:
> >>> Some, llvm for example, has a "*" included.
> >>
> >> Almost certain this is because the package moved
Michael wrote:
> On Thursday 19 December 2024 18:02:29 GMT Matt Connell wrote:
>> On Thu, 2024-12-19 at 11:57 -0600, Dale wrote:
>>> Some, llvm for example, has a "*" included.
>> Almost certain this is because the package moved to a new category.
> Yes, the fine manual says so, check section "eix
On Thursday 19 December 2024 18:02:29 GMT Matt Connell wrote:
> On Thu, 2024-12-19 at 11:57 -0600, Dale wrote:
> > Some, llvm for example, has a "*" included.
>
> Almost certain this is because the package moved to a new category.
Yes, the fine manual says so, check section "eix-diff":
[*N] >>
On Thu, 2024-12-19 at 11:57 -0600, Dale wrote:
> Some, llvm for example, has a "*" included.
Almost certain this is because the package moved to a new category.
Howdy,
It's cold so I booted up my old rig, and NAS box, and was updating the
OS for a little extra heat. I was looking at the output of eix-diff
that is at the end of eix-sync. I'm used to seeing U, N and such but
noticed something new today. Some, llvm for example, has a "*"
included. Like t
6 matches
Mail list logo
