Repository is very big - split? about bunsen-images HOT 15 CLOSED

Wouldn't it be sensible to include all bl-* folders plus icon-avatar/ and svg/ into the default package and just package the wallpapers/ directory separately, the reason being that bl-grub and bl-login are, as their names imply, going to be used in the system anyway (for grub and login purposes, or aren't they by default?). icon-avatar/ and svg/ are basically free anyway.

from bunsen-images.

bl-default contains one image each for grub and login, and four wallpapers (total 5.5MB). That should be enough for a basic setup. bl-grub,login have many more alternative images.

I was thinking about a possible future attempt to build a BunsenLite when bunsen-images-default might be useful. Agreed, icon-avatar and svg could go in too, without adding any extra weight, but bl-login is 9MB by itself, and bl-grub adds another 1MB.

So perhaps bl-login, bl-grub and wallpapers to go in bunsen-images-full?

from bunsen-images.

Wasn't there a previous suggestion to have the basic setup artwork, and the rest in a "bunsen-extras" package?

from bunsen-images.

That's what I'm suggesting here really, but with the big package called bunsen-images-full, or bunsen-images-all or... bunsen-images-extra would be OK too I guess. Or would bunsen-extras have something other than images?

from bunsen-images.

bunsen-images-extra sounds a good descriptive name, but bunsen-extras could include the extra images, as well as future scripts and any other goodies we come up with.

from bunsen-images.

Maybe better to keep the images by themselves? By comparison, scripts are very small and someone who wanted to install some extra gadgets might not want to be obliged also to install 50MB of image files. Maybe a future bunsen-extras (bunsen-doodahs came up for a sound file) for small stuff like scripts?

About naming, I can see two possible patterns:

1. bunsen-images-default which is a hard dependency of bunsen-images-all, so installing just -images-all will automatically bring -images-default as well.

2. bunsen-images-default and bunsen-images-extra. To get the full set a user has to install both packages. OTOH, with this scheme installing -images-extra without images-default is a possibility.

(In both schemes, -images-default will also be a dependency of bunsen-configs.)

I was initially thinking of 1) but maybe there would be users who might prefer 2)?

from bunsen-images.

Revisiting this (while waiting for the repo to clone on my slooow connection :D)

I do not think it makes any sense to split the actual repository as it is. The cloning of this repo would still take as long because the history is being preserved, adding the clone time of the split-out repo. The solution to this: erase the history of this repo (re-commit everything as-it-is minus what we want to split out). Either this or...

Otherwise, I would favour just building two packages, bunsen-images and bunsen-images-extra (using a common pattern in Debian, it's not necessary to name a package 'default').

Thoughts?

from bunsen-images.

I like the idea of two packages bunsen-images and bunsen-images-extra. no scripts in either just images. Keep what comes with the ISO light - half a dozen max ... put the rest in the extra package

from bunsen-images.

Sounds reasonable.
bunsen-images-extra as a bl-welcome option?

from bunsen-images.

That sounds good ... also does BunsenLabs have a DeviantArt page?

from bunsen-images.

I set up a DA BunsenLabs group months ago, just in case anyone else had the idea and grabbed the name ;)
The idea is for it to be a repository for scrots, wallpapers, OB/GTK themes, conkys, tint2s, etc.

I've been waiting for a BL release before publicizing it or uploading anything, but it could be done anytime I guess.

from bunsen-images.

Good Thinking... if you're looking for opinions ... I'd wait until Hydrogen is released to the masses. 👍

from bunsen-images.

To quote @2ion

I would favour just building two packages, bunsen-images and bunsen-images-extra (using a common pattern in Debian, it's not necessary to name a package 'default').

This sounds good. Let's build the two .deb packages out of the same bunsen-images repository. When we get to the point of distributing .deb files instead of source repos then users will have the option of installing only the default set and saving bandwidth/disk space.

from bunsen-images.

@johnraff I did the split. Since the name of bunsen-images doesn't change (including debhelper invocations) I guess we don't have to fix the netinstall script to reflect this right?

from bunsen-images.

It's fine. The script as-is builds both .debs (this is unavoidable and anyway the whole repo is downloaded) then installs bunsen-images only. bunsen-images-extra is left on the user's local repository to install if desired. Anyway, it illustrates the principle, and when we go to debs on a repo the two will be downloadable separately.

from bunsen-images.