Skip to content

Multiple Repository Support#24

Open
lewhfree wants to merge 14 commits intoKindleTweaks:masterfrom
lewhfree:master
Open

Multiple Repository Support#24
lewhfree wants to merge 14 commits intoKindleTweaks:masterfrom
lewhfree:master

Conversation

@lewhfree
Copy link

@lewhfree lewhfree commented Nov 24, 2025

In checkRepositoryFile(), it checks for the file and creates it if it doesn't exist. This should only really happen on first install. It defaults to the official repo at kf.penguins184.xyz. The file is created at /mnt/us/.KFPM/repositories.txt, next to installed.txt. Having the default repo at the top is also good because, in the case of package collisions, it defaults to the first repo, which is the main one.

Both the Go and JS sides respect the repo file.

I'd like to hear comments or changes that need to be made, if any.

Adds a function that loads a filename (Should have the list of repos urls in it) and then loads each one.

It then calls the origional fetch function on each of the repo urls and loads all of those.
Init() was no longer needed, as it was only used on the document start and can be replaced with the new load function
it was used all over, so i just moved it out.
I figured it would make refactoring easier in the future.

I wanted it so I didn't have to pass the url into the loadAll function every time or "hard code" it
I checked the discord roadmap, and thats what its named there. It doesn't matter much.
Not necissary, but it follows the default go code conventions. (My editor auto runs it on save)
It searches all repos instead of the hardcoded one
Move the fetchallrepositories stage to after the check for the file runs.
Should've been parsing by newline. Nothing was showing up on screen because the main repo got split into two urls, both invalid.
@lewhfree
Copy link
Author

I didn't actually make 355 additions and 272 removals; my editor automatically formats the Go on save. It mostly happened in commit 29a56b5, so changes before and after shouldn't be so bad to read. Sorry.

@penguins184
Copy link
Collaborator

I will look over this soon

@lewhfree
Copy link
Author

I've been thinking about this feature a little, and there doesn't seem to be much use for it. It is fairly easy to get a package into the real repository, and the multiple repository might add unnecessary complexity to the codebase. For those reasons, I'm going to close this PR.

@lewhfree lewhfree closed this Dec 11, 2025
@penguins184
Copy link
Collaborator

I'll still look over eventually as it was on the roadmap!

@lewhfree lewhfree reopened this Dec 27, 2025
@penguins184
Copy link
Collaborator

?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants