packages

How To Permanently Blacklist a Package File

Blog post by Barrett on Sun, 2013-12-15 19:17

With the advent of package management and hrev46391, it has become possible to prevent a package from being extracted at boot time.From a suggestion of Matt, and with the contribution of Luroh (thanks!), i would like to explain you how to blacklist a package file in Haiku.

In Haiku's boot menu , there is a 'Blacklist entries' option available. This method will only let you disable system packages, and only until the next time you reboot.

You may know, since the package manager has been added to Haiku, some directories are read only, so unlike the past, isn't possible to just delete the driver. The Blacklist functionality addresses the issue that it may be necessary to remove a problematic file such as a library or a bugged driver, which would otherwise require editing the containing package file.

So let's go to the very simple steps to do that :

  1. Figure out which file in which package you want to blacklist, especially keep in mind if the file is contained in a system package or in a user one.
  2. The second step is to create a text file named 'packages' in /boot/system/settings or in /boot/home/config/settings/global, respectively the first directory is used to blacklist system packages the second is used for user packages.

The final step is to fill the packages file with something like that :

Package 'packagename' {
	EntryBlacklist {
		'entrypath'
		...
	}
}

'packagename' is the name of the package without version, for example 'haiku'.

'entrypath' is an installation location relative path, e.g. "add-ons/Translators/FooTranslator".

This way, blacklisted entries will be ignored by the package_fs. So that they won't appear in the file system.

Let me give a pratical example.

In my case i had the broadcom570x driver to blacklist, so i created the packages file under /boot/system/settings with this content :

Package haiku {
	EntryBlacklist {
		add-ons/kernel/drivers/bin/broadcom570x
	}
}

Then i saved it and rebooted. Once Haiku start the package is re-mounted and the file is ignored by the packagefs.

Hope it was interesting!

Batiseur: not a bed and breakfast

Blog post by jrabbit on Sun, 2011-08-07 15:14

In these last few (official) weeks of Google Summer of Code I’m focusing on the meat of my project. This means that side features like the achievements, scoreboard etc will be ‘frozen’ as-is until after GSOC. I’m planning on rounding them out, just not yet. The main work will be on the builddrone working properly and testing/signing. A major but was in the camlistore python library, I’ve fixed it and will change how it works a little.

I wrote a haikuports standalone validator which can be used in an upcoming version of haikuports possibly or just for your own amusement on a simple bepfile. (Hint you could wrap this in a git-hook and then only allow a commit if your beps pass!) On the builddrone front I fixed a bunch of assumption-related bugs that came from not testing.

BONUS: WPA derived propaganda

GSOC Introduction: Jrabbit, Batisseur and you

Blog post by jrabbit on Thu, 2011-04-28 23:45

I'm Jack (Jrabbit). I am a python hacker.

Bâtisseur is a broad system for making Haiku package development simple and quick. It will borrow concepts from OpenSuse Build and Canonical's Launchpad [Specifically Soyuz]. Some documents pertaining to it can be found in this repo. The end goal will be a modern build system for packages that can scale up or down and a system of achievements for participating in it.

Whats happening now

During the community bonding period I will be working with the new hpkg_builder tool to make sure it's ready for hackage. I will be working with the core team to look at buildbot deployment and such. Also I will be trying to get some of my web tools I wrote for haiku put up on haiku-files.

The Package format

Blog post by Sil2100 on Fri, 2007-06-08 17:07

Personal rant: my university examination session draws near and with it all credit tests as well. I'm doing my best in time management not to put any of my current tasks and projects into starvation, but exactly as Ryan wrote to me - it's not easy.

Going back to more Haiku-specific topics, last week I was mostly analyzing the .pkg format Be Inc. left us behind. After some tests, most crucial parts of it are clear to me now. I must say most of their design solutions for this particular chosen concept had logical and technical grounds. To tell the truth, when I started hacking on this format I thought to myself: “Good god, who did this to you?”. I was wrong. Well... it's a very interesting one nevertheless.

Syndicate content