docs: Add x eget installation method

[lunrenyi]

Add x eget as an installation method for xled.

x eget allows users to install xled directly from its GitHub release:

x eget use excelano/xled

[lunrenyi]

By the way, I'd also like to introduce x-cmd/install.

It is an open-source community dedicated to collecting and maintaining more installation methods for more software.

If your project has an installation method that you'd like to make available to more users, you're welcome to contribute it to the community.

Once added, users can browse and search for available installation methods at x-cmd.com/install, or discover and install these tools directly through the x install command.

Project authors are also very welcome to contribute installation methods for their own projects and share them with the community!

[anderix]

Thanks for this, and for x-cmd — a 4.6k-star toolkit written in awk is a genuinely impressive thing to have built.

I'm going to pass on this one, for a reason about this page rather than about x-cmd. Every install method in that section is one I publish to: the apt repo is mine and signed with my key, the Homebrew tap is mine, and the WinGet manifest and install script point at hashes I generate. x eget use excelano/xled reads my releases page instead, so I'd be documenting a path I don't publish to and can't repair if a future release changes the asset layout. I'd rather not offer readers an install line I can't stand behind.

Two things that might help with the others you've sent: the section opens by saying every install line ends with xled --install-skill, and this snippet doesn't; and it doesn't mention that x itself needs installing first, so a reader following it gets x: command not found. Also the description here says "streamtop" — it looks like it carried over from the previous PR, and h5i and cship have it too.

On the x-cmd/install invitation: that one I'm more open to. I keep my README to channels I publish to myself, but I do carry consumer-side install lines in catalog listings, so a community index is the right slot for it rather than the install section. Let me look at what contributing there involves.

[lunrenyi]

Thanks for the detailed feedback!

That makes sense, and I understand why you'd prefer to keep the README limited to installation methods that you directly publish and maintain. I'll also fix the issues you pointed out.

And thanks for being open to x-cmd/install — I think that's a much better fit for this kind of community-maintained installation method!