openSUSE / openSUSEway

dotfiles for Sway on openSUSE
MIT License
82 stars 17 forks source link

Some missing utilities which could be included #74

Closed mcepl closed 1 year ago

mcepl commented 1 year ago

When discussing https://www.reddit.com/r/openSUSE/comments/w92o0w/comment/ihtrne4/?context=3 I have just checked that we are including in our default sets of packages everything which normal user of sway can use. I have checked packages which I use and which are not included in openSUSEway and sway patterns:

Do we have all included in our standard sets? Is there something else we are missing?

jubalh commented 1 year ago

Update: All 4 packages are available in Factory.

denisok commented 1 year ago

adding them, as part of 0.15-rc .

BTW @mcepl you always could submit package update.

@jubalh I am thinking to add openSUSEway.spec to the repo as well. I know it is kinda dup for the OBS, but actually when adding new stuff it could be handy - so if there is new dependency required - you could add it as part of a PR into the spec file.,

denisok commented 1 year ago

@mcepl I see we have clipman as part of the spec, is that the same as wl-clipboard or different?

mcepl commented 1 year ago

@mcepl I see we have clipman as part of the spec, is that the same as wl-clipboard or different?

stitny~$ rpm -qf /usr/bin/clipman
clipman-1.6.1-1.6.x86_64
stitny~$ rpm -qf /usr/bin/wl-*|sort -u
wl-clipboard-2.1.0-1.4.x86_64
stitny~$ 

https://github.com/yory8/clipman

denisok commented 1 year ago

added in #91

jubalh commented 1 year ago

@jubalh I am thinking to add openSUSEway.spec to the repo as well. I know it is kinda dup for the OBS, but actually when adding new stuff it could be handy - so if there is new dependency required - you could add it as part of a PR into the spec file.,

Yes it makes sense. Makes it easier to track the changes immediately and also for debugging purposes/see when something got added.

FilippoBonazziSUSE commented 1 year ago

How would you handle the OBS update then? osc service manualrun to fetch the new release, then extract and copy out the new spec file?

jubalh commented 1 year ago

That would be an option. I'm also aware that https://github.com/AdamMajer/nodejs-packaging tracks the spec file but didn't check how it is copied/handled. Even worst case with copying it over also doesn't seem to bad to me.

FilippoBonazziSUSE commented 1 year ago

We could also add this sort of out-of-band mechanism:

Add a download_url source service that downloads the spec file from the Github URL https://github.com/openSUSE/obs-service-download_url/blob/master/download_url.service

FilippoBonazziSUSE commented 1 year ago

Follow-up suggestion: the obs-service-extract_file service seems to be exactly what we're looking for.

https://github.com/openSUSE/obs-service-extract_file

denisok commented 1 year ago

there also was a project - to use git as a storage: https://events.opensuse.org/conferences/oSC22/program/proposals/3905

but extracting file from the tarball looks as a good solution - Thanks!

Lets integrate that