HAKILO Repository (for HaikuDepot)

Those who want to download my packages through HaykuDepot can now do it.

Hakilo repository site

Haiku 32bit pkgman add-repo http://repo.hakilo.ru/x86_gcc2
Haiku 64bit pkgman add-repo http://repo.hakilo.ru/x86_64

Now all the decors and controls for the Haiku 32bit are available.
Maybe I’ll post develop-version freepascal and Lazarus to the repository.

On the addition of interesting programs to the repository, I will report in this thread.


Awesome! Thanks for sharing all your work! I’ll definitely give it a try! :smile:

Not sure what I did wrong, but upon trying it, I get an error in the output:

~> pkgman add-repo http://repo.hakilo.ru/x86_64
Fetching repository info from http://repo.hakilo.ru/x86_64 ...
Activating repository config from http://repo.hakilo.ru/x86_64 ...
Error: Failed to open repository file "/boot/system/cache/package-repositories/HAKILO": No such file or directory
Fetching repository checksum from http://repo.hakilo.ru/x86_64 ...
Validating checksum for HAKILO ...
Fetching repository-cache from http://repo.hakilo.ru/x86_64 ...
Validating checksum for HAKILO ...
Activating repository cache for HAKILO ...

I think everything is fine. Refresh and look for packages named “haki …” in HaikuDepot.

If you see the haki_decorator_pack and haki_controllook_pack packages, then everything is OK.


Hey everyone, just wanted to write back and mention to the community that his themes work! This is really incredible, @s40in!

I followed the advice and searched for ‘haki’ in the Depot after adding the repo, and there it was! :slightly_smiling_face:

From there, I got to play with a few of the decors and control looks – these are super cool! Reminds me of the fun decors that Dano used to have! I first tried the game decor (I got the M and L reference after seeing the red and green) :smile: Awesome!

“Next” stop (pun intended) :wink: was the NS theme. Now, everyone in the community knows I’m a Mac/NS lover as well as Be, so seeing this one was super cool! :sunglasses: The square look and medium grays of Haiku’s default decorator goes good with it too.

I also tried out the CDE theme – wow! This looks righteous as well!

And heck, just for the fun of it, I gave in and tried out the Win16 theme, and hey, it looks kind of like Redmond’s 3.x stuff actually. :slight_smile:

But my favorite one I tried out (saved the best for last) was the Hakilo2 and HakiDecorator. These are really nice! I instantly saw some Dano inspiration in here!


Add a dash of Dano’s lavender blues in there (RGB: 118, 120, 184… iirc), lighten the grays a bit, and voila! Definitely keeping this look! (I love how it merges the good parts of Origin with the classic BeOS/Macintosh close buttons, btw).

Definitely recommend everyone tries out the themes from @s40in! This is my first time giving them a whirl, and they’re really cool! Kudos and thanks for creating and sharing them! :smiley:


Can someone make the SkyOS decorator?


@apgreimann, thanks for the detailed review.

Lazarus and freepascal in my Repository.
See the long description of the fpc package in HaikuDepot how copy freepascal settings. This needs to be done only once.

New packges in HAKILO repository for x86_gcc2 Version
fpc_sources_unstable_x86 3.3.1-2
fpc_unstable_x86 3.3.1-2
lazarus_qt5_x86 2.0.2-2
libqt4pas_x86 2.5.1-1
libqt5pas_x86 1.2.6-2

thanks for your work @s40in

Hey uh, your packages cannot be installed on updated Beta 1 anymore. They seem to have a hard requirement for a certain older Beta 1 revision.

Installs just fine here.


1 Like

Here’s what comes up when trying to install a package from the repo:

I did not check it with Haiku B1. I think B1 is no support for changing controllook.

It is strange that you can not choose to “ignore” and put the package. Why then add this element if it cannot be selected?

1 Like

Well, changing control looks is only supported starting with hrev53116 anyway, so it won’t work on beta1.

You should just change the repositorys from b1 to nights upgrade and then will be able to install the control looks

Well would be a fine to have this funktion to ignore this error but it is not wanted. You need to create your packages right. In the most times you get a error like this a package is broken and does not run. To try it, copy it by hand into system/packages.