#101 2025-02-12 11:07:03

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

azote is now purged from my repo. Newer upstream anyway but I'm not prepared to promote it.

labwc/libsfdo is gone from my repo as labwc-0.8.3 will be released 20250221 by @malm which *should* flow on to debian unstable and hopefully make freeze for trixie. Many thanks to Birger Schatt for maintaining labwc at the debian end, and also for adding libsfdo to debian.

mtpaint is also gone, newer upstream and works fine in XII/Wayland

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

eightysixed

Member

From: USA

Registered: 2024-11-24

Posts: 58

Re: BunsenLabs-wayland repository - in development

I'm not sure where to post this, as I couldn't find a thread to post in, and this was the closest thing that I saw when searching for "net install". Anyway, I somehow, accidentally came across this (BunsenLabs Net Install Script).. Holy cow, how long has this been a thing? It looks like it's even being updated. Is this safe use a current base, still?

Awesome. I hope so

e: It's not even in this thread, surprisingly

Last edited by eightysixed (2025-03-11 06:13:28)

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

^It's been there for years, as an alternative installation path.
And yes, it's still being maintained. The Bookworm/Boron netinstall should work OK, but Trixie/Carbon is still a moving target, so anyone playing with that should be prepared to tweak things if necessary.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

eightysixed

Member

From: USA

Registered: 2024-11-24

Posts: 58

Re: BunsenLabs-wayland repository - in development

^It's been there for years, as an alternative installation path.
And yes, it's still being maintained. The Bookworm/Boron netinstall should work OK, but Trixie/Carbon is still a moving target, so anyone playing with that should be prepared to tweak things if necessary.

That's super cool. Probably going on a limb here, but would it work with 32-bit as well?

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

^It's been there for years, as an alternative installation path.
And yes, it's still being maintained. The Bookworm/Boron netinstall should work OK, but Trixie/Carbon is still a moving target, so anyone playing with that should be prepared to tweak things if necessary.

That's super cool. Probably going on a limb here, but would it work with 32-bit as well?

Boron likely would as Bookworm supports 32 bit but 32 bit support (kernels mostly) is dropped from Trixie so Carbon will be a No.

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

As @micko01 says.

Anyway, the netinstall script runs on a previously installed base install of Debian, so whether that's 32bit or 64bit is in the user's hands. In theory you could install a 32bit Debian Bookworm system and then upgrade it to Trixie before running the BL netinstall script, but you'd still be stuck with whatever is the newest 32bit kernel available for Bookworm.

---
Getting Off-Topic but maybe someone would enjoy trying to install the BL Carbon packages on a base of eg 32bit Damn Small Linux?

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

Commit message tells the story:

$ git log
commit 835465dd5f9208a749ee0c3afc0748d163e259a6 (HEAD -> main, origin/main, origin/HEAD)
Author: 01micko <snip>
Date:   Tue Mar 18 07:56:02 2025 +1000

    Updated - qt6gtk2
     - rebuilt against new qt6 libs - thanks to HoaS
    Removed - conky_wl, hyprpicker
     - upstream conky now works on wayland
     - hyprpicker has outdated dependencies - needs new version (todo)

Thanks HoaS - re https://forums.bunsenlabs.org/viewtopic … 49#p142149

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

DeepDayze

Like sands through an hourglass...

From: In Linux Land

Registered: 2017-05-28

Posts: 1,897

Re: BunsenLabs-wayland repository - in development

As @micko01 says.

Anyway, the netinstall script runs on a previously installed base install of Debian, so whether that's 32bit or 64bit is in the user's hands. In theory you could install a 32bit Debian Bookworm system and then upgrade it to Trixie before running the BL netinstall script, but you'd still be stuck with whatever is the newest 32bit kernel available for Bookworm.

---
Getting Off-Topic but maybe someone would enjoy trying to install the BL Carbon packages on a base of eg 32bit Damn Small Linux?

I'd believe the last 32 bit kernel would be 6.11 for Trixie, unless there are 3rd party builds of newer kernels for 32 bit which I doubt there be anyone willing to maintain such builds of 32 bit kernels.

6.12.19 is LTS so would it ever be possible for BL to maintain this version in the BL repos?

Last edited by DeepDayze (2025-03-20 15:06:11)

---

Real Men Use Linux

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

6.12.19 is LTS so would it ever be possible for BL to maintain this version in the BL repos?

Possible yes, but I doubt if anyone would want to take on that extra work and responsibility, especially considering the security aspect. As long as 6.12.19 remains available from a currently maintained Debian repo, with security upgrades, then people can continue using it.

Damn Small Linux is still 32bit compatible.
https://www.damnsmalllinux.org/
https://www.damnsmalllinux.org/2024-download.html

This release candidate is 32 bit compatible and will operate on both 32-bit and 64-bit systems.

AntiX might be another possible 32bit base for BL, but it has more extra contents than DSL, which would need stripping out.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

eightysixed

Member

From: USA

Registered: 2024-11-24

Posts: 58

Re: BunsenLabs-wayland repository - in development

AntiX on super old hardware works quite well. I have it running on a `Dell Inspiron E1705` from 2006

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,063

Website

Re: BunsenLabs-wayland repository - in development

I would recommend OpenBSD for old 32-bit hardware. It's even lighter than the musl libc Linux distributions and hardware support tends to suffer fewer regressions over time because the devs are very cautious about adding new features.

@shep over at daemonforums.org has a setup guide for an openbox/tint2 desktop that could be made to imitate BunsenLabs quite well:

https://daemonforums.org/showthread.php?t=11178

---

Para todos todo, para nosotros nada

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

OpenBSD would be a much further fork away from the current BL than DSL or AntiX, both of which are Debian based. (In fact DSL is based on AntiX.)
So maintaining a BSD version would be a heavy load on BL devs IMO.
It looks like an interesting option for skillful users though, and thanks for the link!

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

eightysixed

Member

From: USA

Registered: 2024-11-24

Posts: 58

Re: BunsenLabs-wayland repository - in development

I would recommend OpenBSD for old 32-bit hardware.

For what it's worth that '09 E1705 was actually an early 64-bit laptop. It weights a ton. I think I payed like $1,500 USD for it in College or something at the time. It has a 17" screen!

But the 32-bit I verified the BL repo to be working 100% fine with is an old 32-bit Acer Aspire One D150 Netbook

edit: That reminds me. It's been awhile since I've reinstalled a fresh copy of Bunsen from the official download. I can't remember, does the installer give you the Option between a "Normal" and "Lite" install? If not, it should

Last edited by eightysixed (2025-03-23 07:02:09)

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

Can we keep on topic please?

I don't mind if there are 32 bit package requests here but whether bunsen supports 32 bit and how going forward is way off topic. If you can't find an appropriate topic make one.

I have some ideas on that also, but am not going to suggest them here.

Thank you.

EDIT
Oh and @eightysixed , thanks for the PM. All good, I just wanted to nip off topic in the butt before it was out of control.

Last edited by micko01 (2025-04-03 09:08:45)

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

It's been awhile since I've reinstalled a fresh copy of Bunsen from the official download. I can't remember, does the installer give you the Option between a "Normal" and "Lite" install? If not, it should.

Sorry to disappoint you, but live-build does not provide the option of multiple file system installs. One squashfs system is what you get, and live-build is what the BL official iso is built from.

As I said above (and caused this thread to go off-topic, sorry @micko01) the netinstall script is there for custom installs.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

I have uploaded 2 icon theme families that are based on Material-Solarized-Suru++. (S++)

The S++ theme as we know it is the one in jgmenu in Boron, that nice iridescent bluish colour. But that icon theme has a secret which not many are privy to. It's all coded in SVG, which are just text files with an XML syntax (you know, XPMs and XBMs are test files with a "C" syntax). This makes it rather easy to edit the colours programatically with a shell script. As a bonus, 10 colour gradients are defined in each individual icon file with a few exceptions, which aren't that important - emotes, flags and such.

So, I wrote a shell script to process S++ into 13 unique icons themes! The ones in S++ are oomox, the default in S++ and  arrongin, aurora, cyberneon, fitdance, rainblue, sunrise, telinkrin, 60spsycho and 90ssummer. I also added bark, sage and grey. The emotes and stuff are split off into a separate themecalled common which the former all depend upon.

Of course there are some missing icons so I modified the labbe-min-icons (now deleted from the repo) and renamed the source package to labbe-min-ng and that produces the same 13 flavours of icon sets, and each depend on there respective Material-Solarized-suru-(flavour).

All are packaged separately so if you install only labbe-min-bark with apt it drags in material-solarized-suru-plusplus-bark and material-solarized-suru-plusplus-common. Likewise with other flavours.

Here's a tree so you can see what's what.

    ├── m
    │   └── material-solarized-suruplusplus-ng
    │       ├── material-solarized-suruplusplus-60spsycho_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-90ssummer_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-arrongin_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-aurora_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-bark_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-common_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-cyberneon_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-fitdance_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-grey_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-ng_12.5-1.debian.tar.xz
    │       ├── material-solarized-suruplusplus-ng_12.5-1.dsc
    │       ├── material-solarized-suruplusplus-ng_12.5.orig.tar.gz
    │       ├── material-solarized-suruplusplus-oomox_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-rainblue_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-sage_12.5-1_all.deb
    │       ├── material-solarized-suruplusplus-sunrise_12.5-1_all.deb
    │       └── material-solarized-suruplusplus-telinkrin_12.5-1_all.deb
    ├── l
    │   └── labbe-min-ng
    │        ├── labbe-min-60spsycho_12.5-1_all.deb
    │        ├── labbe-min-90ssummer_12.5-1_all.deb
    │        ├── labbe-min-arrongin_12.5-1_all.deb
    │        ├── labbe-min-aurora_12.5-1_all.deb
    │        ├── labbe-min-bark_12.5-1_all.deb
    │        ├── labbe-min-cyberneon_12.5-1_all.deb
    │        ├── labbe-min-fitdance_12.5-1_all.deb
    │        ├── labbe-min-grey_12.5-1_all.deb
    │        ├── labbe-min-ng_12.5-1.debian.tar.xz
    │        ├── labbe-min-ng_12.5-1.dsc
    │        ├── labbe-min-ng_12.5.orig.tar.gz
    │        ├── labbe-min-oomox_12.5-1_all.deb
    │        ├── labbe-min-rainblue_12.5-1_all.deb
    │        ├── labbe-min-sage_12.5-1_all.deb
    │        ├── labbe-min-sunrise_12.5-1_all.deb
    │        └── labbe-min-telinkrin_12.5-1_all.deb

Here's the repos.

https://github.com/01micko/material-sol … lusplus-ng

https://github.com/01micko/labbe-min-ng

labwc with labbe-min-bark icons

openbox with labbe-min-bark icons

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

Awesome work, @micko01!

I think, after a pause for reflection and recuperation, we should migrate copies of at least the bark and sage variants, and possibly all of them, to the official BL repos so we can use them in the default Carbon desktop. What do you think?

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

Awesome work, @micko01!

I think, after a pause for reflection and recuperation, we should migrate copies of at least the bark and sage variants, and possibly all of them, to the official BL repos so we can use them in the default Carbon desktop. What do you think?

Sure!

Anyway here's some samples.

labbe-min-[sage,bark,oomox,grey] in that order These can be defaults if you like, but the source needs to be altered, no big deal. Same for the S++

labe-min-[sunrise,rainblue,cyber-neon,aurora,90ssummer,telinkrin,fitdance,arrongin,60spsycho]

material-solarized-suruplusplus-[bark,sage,oomox,grey]

material-solarized-suruplusplus-[60spsycho,arrongin,oomox,telinkrin,90ssummer,aurora,cyberneon,rainblue,sunrise]

Last edited by micko01 (2025-04-02 11:06:30)

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

^OK two topics here, I guess:
1) What to make available in the official Carbon repos.
2) Choice for Carbon default.

For 1) I'd say, as long as they're packaged into smallish .debs (each with one theme or a few related ones together) then the more the merrier. Let's have the default themes by themselves though, to get the minimal install as small as possible.

2) Since the Bark and Sage themes (GTK and wallpaper) have been set already let's choose either labbe-min-[bark,sage] or material-solarized-suruplusplus-[bark,sage].

Personally, I'm happy with either of those, but I think graphics boss @hhh should have the final say. Not only because I have little to no artistic sense, but, even more, I think if one person has the final call on the graphics stack we have a better chance of a consistent-looking desktop.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

^OK two topics here, I guess:
1) What to make available in the official Carbon repos.
2) Choice for Carbon default.

For 1) I'd say, as long as they're packaged into smallish .debs (each with one theme or a few related ones together) then the more the merrier. Let's have the default themes by themselves though, to get the minimal install as small as possible.

Ok, but "smallish" for the whole lot of S++, including the source package is around 80MB!
labbe is quite smaller at around 800kB.
You can check the calculations

mick@dellhome:~/Github/zbuild/material$ for i in *.deb *.tar.gz; do echo $i;stat -c %s $i;done
material-solarized-suruplusplus-60spsycho_12.5-1_all.deb
1928940
material-solarized-suruplusplus-90ssummer_12.5-1_all.deb
1929812
material-solarized-suruplusplus-arrongin_12.5-1_all.deb
1928672
material-solarized-suruplusplus-aurora_12.5-1_all.deb
1927112
material-solarized-suruplusplus-bark_12.5-1_all.deb
1923972
material-solarized-suruplusplus-common_12.5-1_all.deb
156500
material-solarized-suruplusplus-cyberneon_12.5-1_all.deb
1929580
material-solarized-suruplusplus-fitdance_12.5-1_all.deb
1928616
material-solarized-suruplusplus-grey_12.5-1_all.deb
1925440
material-solarized-suruplusplus-oomox_12.5-1_all.deb
1924244
material-solarized-suruplusplus-rainblue_12.5-1_all.deb
1927492
material-solarized-suruplusplus-sage_12.5-1_all.deb
1924552
material-solarized-suruplusplus-sunrise_12.5-1_all.deb
1925952
material-solarized-suruplusplus-telinkrin_12.5-1_all.deb
1929816
material-solarized-suruplusplus-ng_12.5.orig.tar.gz
46
material-solarized-suruplusplus-ng-12.5.tar.gz
65640207
---
mick@dellhome:~/Github/zbuild/labbe-ng$ for i in *.deb *.tar.gz; do echo $i;stat -c %s $i;done
labbe-min-60spsycho_12.5-1_all.deb
14740
labbe-min-90ssummer_12.5-1_all.deb
14708
labbe-min-arrongin_12.5-1_all.deb
14652
labbe-min-aurora_12.5-1_all.deb
14612
labbe-min-bark_12.5-1_all.deb
14764
labbe-min-cyberneon_12.5-1_all.deb
14752
labbe-min-fitdance_12.5-1_all.deb
14668
labbe-min-grey_12.5-1_all.deb
14616
labbe-min-oomox_12.5-1_all.deb
14684
labbe-min-rainblue_12.5-1_all.deb
14616
labbe-min-sage_12.5-1_all.deb
14644
labbe-min-sunrise_12.5-1_all.deb
14608
labbe-min-telinkrin_12.5-1_all.deb
14808
labbe-min-ng_12.5.orig.tar.gz
24
labbe-min-ng-12.5.tar.gz
619222

We can weed out similar themes easily enough and probably reduce the size by 40 - 50%.

2) Since the Bark and Sage themes (GTK and wallpaper) have been set already let's choose either labbe-min-[bark,sage] or material-solarized-suruplusplus-[bark,sage].

That makse sense of course

Personally, I'm happy with either of those, but I think graphics boss @hhh should have the final say. Not only because I have little to no artistic sense, but, even more, I think if one person has the final call on the graphics stack we have a better chance of a consistent-looking desktop.

Absolutely! At risk of veering off, I think further discussion of what and what not to include should go to the  Carbon Themes (beta version) discussion and await @hhh 's opininion.

As far as my artistic sense goes, designing stuff in code is about the only way I know how.

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen