LINUX LITE 7.4 FINAL RELEASED - SEE RELEASE ANNOUNCEMENTS SECTION FOR DETAILS


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ukbrian's: Ikey on G+ at 3:17 PM 14/02/26
#1
Ikey on G+ at 3:17 PM 14/02/26 after a week away from evolve
Quote:My week is nearly up. We've been experimenting with a lot of things this week, and among the visible changes is Wayland compatibility.
https://www.linuxliteos.com/forums/index...8#msg12168

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

Ubuntu + Budgie info
https://plus.google.com/108504253507350757415
Reply
#2
Ikey quote
Quote:So, MASSIVE eureka moment, but.. Evolve OS packaging just got *drastically* simplified.
https://evolve-os.com/forums/viewtopic.php?f=21&t=323

Looking like his adoption of PiSi was right!
Reply
#3
Ikey on G+ at 3:17 PM 14/02/26 after a week off to think

Quote:My week is nearly up. We've been experimenting with a lot of things this week, and among the visible changes is Wayland compatibility.

Going forward (at some point, not immediately, gotta prioritise Wink) - the core of Budgie Desktop will be written in C. budgie-wm is already C, and the sheer bulk of code in Budgie is within our applets. There's no real harm these staying in Vala.

However, this rewrite will also see the introduction of Wayland compatibility. How's it work? P simple. Just use a whacking great big window when we need menus and such on screen. Problem genuinely solved. Smile

Also going forward, we'll be switching from our existing pspec.xml/actions.py build format to ypkg as our primary format.

Currently ypkg is written in Python (as is eopkg) - however this presents a number of problems. Firstly I have a stick up my arse about Python performance anyway and we need an accessible API, which means using a language all other languages can interface with, thus C. And C is freakin awesome anyway Wink

So, what exactly is ypkg? Well right now it does a lot of magic to build packages from an incredibly simple format into something eopkg/pisi can understand. Then we thought.. well, we've got a superior concept here...

This merges some concepts from RPM packaging and PKGBUILD files, but using YAML. Secondly, subpackages, dependencies and such are an automated thing! Coz aint nobody got time for that. Build dependencies are something that are still manual, because this build format is post-packaging, *not* automated packaging!!

Current proof of concept for ypkg is here:
https://github.com/evolve-os/ypkg

Given the fact its a far superior build format than eopkg/pisi - and we want a C API - going forward we'll be making ypkg our long-term replacement to eopkg.

Contrary to other supa-awesome-pow! package managers, there's a lot of features we don't care for. Evolve OS isn't "one of those distros" - so we don't need 15 different combination of flags for awesome features in a package manager. We're looking at like-for-like and dropping of side-baggage, as well as simplifying things.

I hate the bluey background and the small font size that makes it hard to read, it's text I want, desire to read it in comfort not struggle to read minute letters!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)