Feature: Installation and update about hyde-cli HOT 30 OPEN

Yes it requires sudo so that it will be available systemwide.

from hyde-cli.

nah not necessary but a typical linux person would definitely type hyde after installing as the aur name is also hyde-cli-git .

from hyde-cli.

that makes sense. lets get on with the remaining milestones . I could help out on my free time with some issues

from hyde-cli.

@kRHYME7 cool. Will try out. It was a pain to maintain the usage file as we are adding so many things .

from hyde-cli.

This is exclusive for --dev (contributors)

so Hyde --dev select the gen completion then it will output the Hyde.usgae in the terminal (stdou).

or just using ./complgen.sh

from hyde-cli.

Soon will change the goal of this project. At first, it only acts as helper and workarounds, but I guess we should consider turning this project as a wrapper for Hyde.

from hyde-cli.

I think we should make the cli as preferred option for installing dots in the readme . And the git clone as manual

from hyde-cli.

tl;tr

Not yet, for now. As the CLI is dependent on some install scripts from Hyde.
I am now considering an independent one in case we can't follow the breaking changes upstream.

Expect a markdown for these soon in README.

Hyde-install
Done:

• shell selection
• patching themes
• Sddm theme selectiom
• Restoring configs

not yet:

• nvidia handling ( will steal it from upstream or I'm considering forking the endeavorOS nvidia-inst pkg )
  Can you check if it's legal? I already tested it on my local and it works. I'm hesitant because no one ported this packaeg to AUR. (nvidia-inst AUR is ready too, in my local machine 😄)
• GRUB, (will copy upstream lol)

What's on my plate:

• Hyde-TUI templating (for declarative formats for devs - just bash lol )
• Package installation

1. Everything works now my only issue is I really want to store the package array inside a variable not a file so that it will be faster than writing multiple files. (Just my ego and proof of concept)
2. We can write it all in memory, drawbacks are We should execute everything in a single shell , or do some exports.

Will try 2 this week if it's too much then will use the first method.

I made a fast sketch:

NOTE
consider --[flags] to be invoked manually and consciously, this gives freedom without breaking the defaults for unconscious inputs.

from hyde-cli.

Also, I think we should rename the cli from "Hyde" to "hyde" , most clis have small case naming patterns

from hyde-cli.

Also another thing, the make version of the install requires you to sudo. Is it okay?

from hyde-cli.

about the Command being Uppercase, It's for clarity and being conscious of what the user types in the Terminal.

is it really necessary to make it lowercases?

from hyde-cli.

Will leave it like that for now.

My convention for this is like

1st: Main Command
2nd: Actual function
3rd: [args/params]

For me this is too long, so I decided to make the first command stand out, indicating that this is the main Shell. Something like that. Will definitely make it lowercase if 2 or more requested it. ( inspired byt the Compositor command Hyprland )

from hyde-cli.

I'm just annoyed with the Hyde.usage haha.
I'm thinking of breaking it down to single file for each funtions. eg upgrade restore etc
then will make a script to merge them later on, plus compile with complgen. It is not a perfect solution,
But will make it easier for me and other contributors to find the function via file, then add its related function.

Another thing can we use endeavorOS nvidia-inst?
https://github.com/endeavouros-team/PKGBUILDS/blob/master/nvidia-inst/nvidia-inst

from hyde-cli.

@rubiin Hello! the Hyde.usage now is auto generated

from hyde-cli.

I was thinking of adding jp2a dependency when installing from aur for seamless experience

from hyde-cli.

This is used to render images in ascii right?

from hyde-cli.

yup. Having it will dependency will make the CLI workable straightforward

from hyde-cli.