BunsenLabs-wayland repository - in development

micko01 · 2024-06-26 08:29:26

@hhh merged PR, merged into repo and all looks good

Many thanks!

Seems like my workflow is ok, which is:

* merge PR (if suitable)
* pull locally
* cd debian/
* reprepro include{deb,dsc,changes} ../pkg/pkg_ver-0.1_arch.[type]
* cd ../
* rm -r pkg
* git add [stuff - I usually use . (dot) - adds all changes]
* git commit
* git push

Voila!

hhh · 2024-06-26 12:03:39

@micko01, cool.

Typo on your Links page... PGP puplic key (public, of course).

Add a link to this thread there? Also, maube point the github repo to "Links" instead of "Home"?

Also, there probably should be a page about what's available on the repo and a summary of what the package is. I had included an amended/abbreviated README about Hyprlock (gone now that I synced my fork to your main).

I'll start adding a proper description in my control files,so far I've been focused on getting the packages to build successfully and relearning GitHub. Now I'm delving deeper into the manual and will start learning all the "Debian way" details.

---

Next PR incoming from me, hyprpicker, a cli color picker that works on wlroots.

hhh · 2024-06-26 13:25:14

I'm running Debian sid. I can confirm that running the setup script from https://01micko.github.io/links.html and then 'sudo apt update' sets up @micko's repo, with the 01micko.sources in /etc/apt/sources.list.d/

I purged my local hyprlang/hyprlock packages and ran..

lab@wayland:~$ sudo apt install hyprlock
[sudo] password for lab: 
Installing:                     
  hyprlock

Installing dependencies:
  hyprlang

Summary:
  Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
  Download size: 0 B / 286 kB
  Space needed: 882 kB / 21.8 GB available

Continue? [Y/n]

Result...

lab@wayland:~$ apt policy hyprlock
hyprlock:
  Installed: 0.3.0-0.1
  Candidate: 0.3.0-0.1
  Version table:
 *** 0.3.0-0.1 500
        500 https://01micko.github.io/debian trixie/main amd64 Packages
        100 /var/lib/dpkg/status
lab@wayland:~$ apt policy hyprlang
hyprlang:
  Installed: 0.5.2-0.1
  Candidate: 0.5.2-0.1
  Version table:
 *** 0.5.2-0.1 500
        500 https://01micko.github.io/debian trixie/main amd64 Packages
        100 /var/lib/dpkg/status
lab@wayland:~$

Awesome work, @micko01! Great input, @johnraff!

hhh · 2024-06-26 14:02:56

hyprpicker PR is in.

https://github.com/hhhorb/01micko_hhhor … hyprpicker

johnraff · 2024-06-26 23:57:46

This repo is now automatically added when running the carbon-wayland branch of the netinstall script:
https://github.com/BunsenLabs/bunsen-ne … on-wayland
See: https://github.com/BunsenLabs/bunsen-ne … ces.list.d
I just dropped micko's 01micko.sources file in sources.list.d
I haven't done a test run yet, but given no typos, i think it should work.

@micko that could be an alternative way for people to enable this repo - if you provided a 01micko.sources for download, people could just copy it into place:

wget https://01micko.github.io/01micko.sources
sudo cp 01micko.sources /etc/apt/sources.list.d/

Maybe a bit simpler than downloading and running a script?

---
At present the carbon-wayland netinstall script installs the regular carbon X-based setup, but with help from @micko01 that will change...

Last edited by johnraff (2024-06-27 00:05:59)

micko01 · 2024-06-27 08:16:23

hhh wrote:

@micko01, cool.
Typo on your Links page... PGP puplic key (public, of course).

Fixed :woops:

hhh wrote:

Add a link to this thread there? Also, maube point the github repo to "Links" instead of "Home"?

Done!

hhh wrote:

Also, there probably should be a page about what's available on the repo and a summary of what the package is. I had included an amended/abbreviated README about Hyprlock (gone now that I synced my fork to your main).

I still have those READMES. I'll think about what to do there but maybe a man page in configs? Basic of course.

hhh wrote:

I'll start adding a proper description in my control files,so far I've been focused on getting the packages to build successfully and relearning GitHub. Now I'm delving deeper into the manual and will start learning all the "Debian way" details.
---
Next PR incoming from me, hyprpicker, a cli color picker that works on wlroots.

Merged and up.

micko01 · 2024-06-27 08:52:30

Many thanks @johnraff

johnraff wrote:

This repo is now automatically added when running the carbon-wayland branch of the netinstall script:
https://github.com/BunsenLabs/bunsen-ne … on-wayland
See: https://github.com/BunsenLabs/bunsen-ne … ces.list.d
I just dropped micko's 01micko.sources file in sources.list.d
I haven't done a test run yet, but given no typos, i think it should work.
@micko that could be an alternative way for people to enable this repo - if you provided a 01micko.sources for download, people could just copy it into place:
wget https://01micko.github.io/01micko.sources
sudo cp 01micko.sources /etc/apt/sources.list.d/
Maybe a bit simpler than downloading and running a script?

I like it both ways

On it.

Reminds me of this Australian band's song. Youtube link. You may have (or probably haven't) heard it!

johnraff · 2024-06-28 06:09:30

johnraff wrote:

This repo is now automatically added when running the carbon-wayland branch of the netinstall script:
https://github.com/BunsenLabs/bunsen-ne … on-wayland
See: https://github.com/BunsenLabs/bunsen-ne … ces.list.d
I just dropped micko's 01micko.sources file in sources.list.d
I haven't done a test run yet, but given no typos, i think it should work.

Did a VM install and it worked.
micko01 repo available:

Of course it's still an X-based desktop that gets installed, but the framework is there for turning it into a Wayland installer.
It might not take more than swapping some apps, and maybe adding some user configs.
Of course, there might be more to it than that...

micko01 · 2024-06-29 05:01:50

hhh wrote:

hyprpicker PR is in.
https://github.com/hhhorb/01micko_hhhor … hyprpicker

.. and here's a sweet little yad frontend

bl-hyprpicker

#!/bin/bash

find_color() {
    printf "%d" "0x${1}"
}

_get() {
    col_in="$1"
    echo -e '<?xml version="1.0" encoding="UTF-8"?>
<svg xmlns="http://www.w3.org/2000/svg" version="1.1"  height="48px" width="48px" viewBox="0 0 48 48">
  <path d="m 0 0 48 0 0 48 -48 0 z" style="fill:'$col_in';stroke:none;"/>
</svg>' > $TEMPDIR/col.svg
    BCOL=${col_in/\#/}
    BR=${BCOL:0:2}; BG=${BCOL:2:2}; BB=${BCOL:4:2};
    BHR=$(find_color $BR)
    BHG=$(find_color $BG)
    BHB=$(find_color $BB)
    ZC='rgb('$BHR','$BHG','$BHB')'
    BHR=$(dc -e'3k '$BHR' 255 / p')
    BHG=$(dc -e'3k '$BHG' 255 / p')
    BHB=$(dc -e'3k '$BHB' 255 / p')
    X=''
    [ ${BHR:0:1} = '.' ] && X=0
    [ ${BHG:0:1} = '.' ] && X=0
    [ ${BHB:0:1} = '.' ] && X=0
    ZF=''$X$BHR' '$X$BHG' '$X$BHB''
    yad --title="Color Picker" --name="select-color" --form \
    --image="$TEMPDIR/col.svg" --text=" Copy and paste color found\n to your application:" \
    --field="Color Hex" "$col_in" \
    --field="Color RGB" "$ZC" \
    --field="Color sRGB" "$ZF" \
    --button="Ok!gtk-ok":0
    return 0
}

export -f find_color _get

export TEMPDIR
TEMPDIR=$(mktemp -d /tmp/colpickXXXX)

# cleanup
trap "rm -rf $TEMPDIR" EXIT

_get $(hyprpicker)

Edit for pic

Edit to add:

based on wly-colpick

Last edited by micko01 (2024-06-29 05:25:18)

micko01 · 2024-06-29 05:14:42

johnraff wrote:

johnraff wrote:
This repo is now automatically added when running the carbon-wayland branch of the netinstall script:
https://github.com/BunsenLabs/bunsen-ne … on-wayland
See: https://github.com/BunsenLabs/bunsen-ne … ces.list.d
I just dropped micko's 01micko.sources file in sources.list.d
I haven't done a test run yet, but given no typos, i think it should work.
Did a VM install and it worked.
micko01 repo available:
https://imgur.com/c37JgU1m.png
Of course it's still an X-based desktop that gets installed, but the framework is there for turning it into a Wayland installer.
It might not take more than swapping some apps, and maybe adding some user configs.
Of course, there might be more to it than that...

While it's still early days of the repo, I'm thinking I should change the name of it; that really means deleting and rebuilding, which is a good thing anyway because I can fix up debian versioning.

Thoughts? And what about the name? 'carbon-wayland'? I'm fine with that.

johnraff · 2024-06-29 05:52:38

"carbon-wayland" is the name of the bunsenlabs-netinstall branch. It might be confusing to some people if your repo had the same name?

Anyway, I don't see a name anywhere - the url is https://01micko.github.io/debian/ are you planning to change that? Or do you mean change the name of your GitHub repo from 01micko.github.io to something else? Or do you mean change the name of the suite from "trixie" to "carbon-wayland"?

If you intend it to be very BunsenLabs focussed, and also to be taken down before the next Nitrogen release, then Carbon-something might work, but if you want to avoid more work down the road I might suggest a totally neutral sort of name that people on other projects could use and that stayed usable in the future.

johnraff · 2024-06-29 05:55:48

Re: hyprpicker and bl-hyprpicker, great work guys, but you know yad already has 'yad --color' ?
https://forums.bunsenlabs.org/viewtopic … 02#p135602
It looks as if it might do the job already.

micko01 · 2024-06-29 06:38:04

johnraff wrote:

"carbon-wayland" is the name of the bunsenlabs-netinstall branch. It might be confusing to some people if your repo had the same name?

I'm open to names. carbon-13, carbon-testing, testing (this is for reprepro) - whatever.

johnraff wrote:

Anyway, I don't see a name anywhere - the url is https://01micko.github.io/debian/ are you planning to change that? Or do you mean change the name of your GitHub repo from 01micko.github.io to something else? Or do you mean change the name of the suite from "trixie" to "carbon-wayland"?

So yeah, change from 'trixie'. I'm not creating another github repo, so that can stay as is.

johnraff wrote:

If you intend it to be very BunsenLabs focussed, and also to be taken down before the next Nitrogen release, then Carbon-something might work, but if you want to avoid more work down the road I might suggest a totally neutral sort of name that people on other projects could use and that stayed usable in the future.

I don't see a problem with anyone using it. The only problem is that I don't want to violate githubs bandwith and storage limits which are 100GB and 1GB respectively. When all packages reach trixie I intend to remove them and if they don't they can stay indefinitely subject to the above limitations.

micko01 · 2024-06-29 06:48:42

johnraff wrote:

Re: hyprpicker and bl-hyprpicker, great work guys, but you know yad already has 'yad --color' ?
https://forums.bunsenlabs.org/viewtopic … 02#p135602
It looks as if it might do the job already.

Yes it's just a gtk-colorbutton, same as in many gtk programs including geany. The eye dropper doesn't work in wayland so that's where this comes in. BTW; GIMPS gtk2 eye dropper fails miserably also.

I wrote one ages ago that depends on wayland tools (slurp - a region selector and grim - a screenshot tool) and netpbm (what a great piece of software that is!) and re-wrote it in yad. That imgur prog I was working on uses 'pamscale' - a program in netpbm - to scale the image for upload because the basic wayland tools lack that feature.

johnraff · 2024-06-29 07:00:46

^yad's eye-dropper doesn't work on wayland? I guess it's just importing a GTK3 library that doesn't work? I that case, sure a replacement is needed.

johnraff · 2024-06-29 07:25:29

micko01 wrote:

johnraff wrote:
Anyway, I don't see a name anywhere - the url is https://01micko.github.io/debian/ are you planning to change that? Or do you mean change the name of your GitHub repo from 01micko.github.io to something else? Or do you mean change the name of the suite from "trixie" to "carbon-wayland"?
So yeah, change from 'trixie'. I'm not creating another github repo, so that can stay as is.

Ah the suite name. OK got it. I was wondering about "trixie" to be honest. Our boron-backports repo uses the suite name "bookworm-backports". This is so if we backport some Debian package and put it there we won't need to also backport any dependencies which might be in Debian's bookworm-backports. Users can run 'apt install -t bookworm-backports <package>' and have packages pulled in from both the BL and Debian backports repos.

In your case, though, I'm not quite sure. It might well be that there's no advantage in naming your suite "trixie", and you could call it anything you like. The suite name will go in 01micko.sources so users won't have any extra work - except possibly those that have already enabled your repo. Changing later on will be even more work, so I wouldn't hurry this. Give it some thought.

johnraff wrote:
If you intend it to be very BunsenLabs focussed, and also to be taken down before the next Nitrogen release, then Carbon-something might work, but if you want to avoid more work down the road I might suggest a totally neutral sort of name that people on other projects could use and that stayed usable in the future.

Now I see you mean the suite, my suggestion right now would be "trixie-<something>" since the packages in this suite are meant to be used on trixie. I don't think anyone here would mind you calling it carbon-<something> either, but why restrict your potential users to BL? I personally would prefer you avoided "carbon-wayland", just in case we need that suite name for an official BL repo further down the road.

The only problem is that I don't want to violate githubs bandwith and storage limits which are 100GB and 1GB respectively. When all packages reach trixie I intend to remove them and if they don't they can stay indefinitely subject to the above limitations.

I wouldn't worry too much at this stage, unless you plan to host some chubby things. The BL reprepro debian/ directory is currently ~850MB with all the Lithium, Beryllium, Boron and Carbon packages.

marens · 2024-06-29 13:02:20

micko01 wrote:

Yes it's just a gtk-colorbutton, same as in many gtk programs including geany. The eye dropper doesn't work in wayland so that's where this comes in. BTW; GIMPS gtk2 eye dropper fails miserably also.

johnraff wrote:

^yad's eye-dropper doesn't work on wayland? I guess it's just importing a GTK3 library that doesn't work? I that case, sure a replacement is needed.

This should work in Wayland.
Maybe not perfect (like gcolor2), but if there is no better solution:

zenity --color-selection

Note*
I don't use Wayland and can't test.

Last edited by marens (2024-06-29 13:06:40)

hhh · 2024-06-29 13:11:04

johnraff wrote:

^yad's eye-dropper doesn't work on wayland? I guess it's just importing a GTK3 library that doesn't work? I that case, sure a replacement is needed.

yad --color

(yad:90020): Gdk-CRITICAL **: 09:08:29.567: gdk_x11_window_get_xid: assertion 'GDK_IS_X11_WINDOW (window)' failed

(yad:90020): Gdk-WARNING **: 09:08:31.605: Window 0x556d33421e40 is already mapped at the time of grabbing. gdk_seat_grab() should be used to simultanously grab input and show this popup. You may find oddities ahead.

hhh · 2024-06-29 13:19:59

marens wrote:

This should work in Wayland.
Maybe not perfect (like gcolor2), but if there is no better solution:
zenity --color-selection
Note*
I don't use Wayland and can't test.

Doesn't work.

zenity --color-selection

Gtk-Message: 09:12:10.090: GtkDialog mapped without a transient parent. This is discouraged.

hyprpicker works perfectly.

@micko01, I get an error with your script...

sh pick.sh
pick.sh: 36: export: Illegal option -f

... but maybe I'm not understanding how to use it. Where's the call to hyprpicker?

marens · 2024-06-29 13:35:50

^ I guess this doesn't work either:

GDK_BACKEND=x11 inkscape

OR*

env GDK_BACKEND=x11 yad --color

env GDK_BACKEND=x11 zenity --color-selection

Last edited by marens (2024-06-29 16:48:21)

#21 2024-06-26 08:29:26

Re: BunsenLabs-wayland repository - in development

#22 2024-06-26 12:03:39

Re: BunsenLabs-wayland repository - in development

#23 2024-06-26 13:25:14

Re: BunsenLabs-wayland repository - in development

#24 2024-06-26 14:02:56

Re: BunsenLabs-wayland repository - in development

#25 2024-06-26 23:57:46

Re: BunsenLabs-wayland repository - in development

#26 2024-06-27 08:16:23

Re: BunsenLabs-wayland repository - in development

#27 2024-06-27 08:52:30

Re: BunsenLabs-wayland repository - in development

#28 2024-06-28 06:09:30

Re: BunsenLabs-wayland repository - in development

#29 2024-06-29 05:01:50

Re: BunsenLabs-wayland repository - in development

#30 2024-06-29 05:14:42

Re: BunsenLabs-wayland repository - in development

#31 2024-06-29 05:52:38

Re: BunsenLabs-wayland repository - in development

#32 2024-06-29 05:55:48

Re: BunsenLabs-wayland repository - in development

#33 2024-06-29 06:38:04

Re: BunsenLabs-wayland repository - in development

#34 2024-06-29 06:48:42

Re: BunsenLabs-wayland repository - in development

#35 2024-06-29 07:00:46

Re: BunsenLabs-wayland repository - in development

#36 2024-06-29 07:25:29

Re: BunsenLabs-wayland repository - in development

#37 2024-06-29 13:02:20

Re: BunsenLabs-wayland repository - in development

#38 2024-06-29 13:11:04

Re: BunsenLabs-wayland repository - in development

#39 2024-06-29 13:19:59

Re: BunsenLabs-wayland repository - in development

#40 2024-06-29 13:35:50

Re: BunsenLabs-wayland repository - in development

Board footer