@tulili hi, I can't respond on github atm but the bling module only pulls in the items specified, su

@tulili hi, I can't respond on github atm but the bling module only pulls in the items specified, sure it's copied into the image, but it's in /tmp, so all of the rpms are removed from the image. Only the ones that are installed are kept inside the image (specified in bling module) bling module also isn't needed in the recipe.yml

GerbleshOP•9/10/23, 1:30 AM

This also isn't too streamlined, but technically one could define their own repo and add it in the container file, and write an installer script in modules. Would work just fine

tulip•9/10/23, 1:38 AM

Oh hi!

GGerblesh @tulili hi, I can't respond on github atm but the bling module only pulls in the...

tulip•9/10/23, 1:40 AM

No, no, it wasn't exactly that that I was trying to convey, I just thought that maybe by separating where the modules are declared from the repos themselves might be a good idea

tulip•9/10/23, 1:41 AM

Like, before all files that were cloned onto the images based off of StartingPoint were declared in their own repos, and that made updating things like the ublue-nix-install script a lot worse, since it wasn't necessarily centralized onto one repo (in this case, bling!)

tulip•9/10/23, 1:43 AM

I just thought that maybe my moving the "modules" folder in the Startingpoint template to other repo, like bling, we could have a better way to keep everyone up-to-date with their module implementations, without requiring them to sync their repos with github's fork thing (which can be very annoying at times when merge conflicts happen)

tulip•9/10/23, 1:45 AM

Having this pattern someone could just clone their own if they want, too

Ttulip I just thought that maybe my moving the "modules" folder in the Startingpoint te...

GerbleshOP•9/10/23, 1:50 AM

So adding the bling module from the containerfile?

GerbleshOP•9/10/23, 1:50 AM

The module being contained in the repo?

tulip•9/10/23, 1:51 AM

Hmmmm how can I explain it

tulip•9/10/23, 1:52 AM

instead of having this folder at the individual repo level, we could just clone it in the Containerfile from ublue-os/bling:latest

tulip•9/10/23, 1:52 AM

like we can already do with other files in the "files" folder in that image

tulip•9/10/23, 1:53 AM

so all standard modules used in startingpoint are defined there and cloned by everyone

tulip•9/10/23, 1:55 AM

something like this!

tulip•9/10/23, 1:58 AM

having that, someone could just extend the pattern like this

Ttulip something like this!

GerbleshOP•9/10/23, 2:02 AM

I like the idea of fetching modules, but we need to figure out how we do documentation for them

GerbleshOP•9/10/23, 2:02 AM

Since currently documentation is in-repo

tulip•9/10/23, 2:03 AM

oh.....

tulip•9/10/23, 2:03 AM

yeah that is an issue

GerbleshOP•9/10/23, 2:08 AM

It also makes it harder to modify stock modules. I like the idea for the blingbling module, as it relies on the bling repo already, but the other modules don't rely on external repos

GerbleshOP•9/10/23, 2:13 AM

@hermmm probably has some ideas on this. Moving the docs into the website would probably be the best course of action if we were to fetch modules from a separate repo. Though I dunno if that repo should be bling itself

xyny•9/10/23, 7:22 AM

Hey @tulili and @Gerblesh ! I actually thought about this, but didn't consider the modules angle. Putting them in bling with the docs pulled onto the website would serve really well! The reason I didn't think about it, though, is because I kind of want startingpoint to be a self-contained system. But I guess that's not as noble of a goal as better portability. The docs is a non-issue since other README's are already pulled there, could reutilize the same codre

xyny•9/10/23, 7:23 AM

My secret future plans were to, once startingpoint becomes too big, create a marketplace action that does everything startingpoint does but without having all the code in the repo.

xyny•9/10/23, 7:23 AM

But I guess that could be done even with the modules in bling.

xyny•9/10/23, 7:24 AM

And creating your own modules wouldn't be that big of a deal. There'd still be a module folder local to your repository, it'd just be empty.

xyny•9/10/23, 7:25 AM

But the merge conflicts angle is unlikely, since modules are not intended for the user to change. But I guess someone might want to add extra features to a module.