[haiku-development] Re: [haiku] Package Manager:

Fredrik Holmqvist wrote:
> 2012/5/21 Ingo Weinhold <ingo_weinhold@xxxxxx>:
> > If you want to work on package management that would certainly be nice. If 
> > you have questions feel free to ask. Though not as complete and detailed as 
> > it could be, there already is quite a bit of documentation on package 
> > management in the wiki [1], so, if you haven't read it, I'd wholeheartedly 
> > recommend to do so. Oliver and I have tried to keep it up to date (also 
> > feel free to extend it).
> 
> I have been reading and trying to figure out if it possible to work
> on, or at least play around with to get a feeling for it. As you
> mention above a deeper understanding is needed, which may make this
> hard.
> 
> From what I can gather the current code lives in
> https://github.com/weinhold/ under Haiku (in one or more of the
> branches pm-flat or package-management) and buildtools (branch
> package-management).
> 
> Is it in a state worth checking out and building?

It should build and work fine, if that's what you mean.

> If yes, what
> branches should be used and are there anything special needed to do
> this?

The Haiku pm-flat branch is the right one (the package-management branch is 
obsolete and I should delete it when I get to it) and the buildtools 
package-management branch. With the exception that only gcc2 builds are 
possible building works as usual.

> (I see on the wiki there are forks for haiku-porter and ports as
> well).

Indeed, they are for moving to building proper HPKG files for the optional 
packages instead of zip files.

> Are there tasks that can be done by other devs that can be added as
> trac tickets?

Just like the expander TODO (#8494) the build system TODO (identify files 
before copying to the image) is independent of package management as well. 
There are other issues that result from the read-only state of the packagefs. 
Tracker using file attributes to store view state information is one that is 
less important ATM, though it has to be solved eventually (at the latest with 
the introduction of multi-user). There probably are other issues of that kind 
that I don't know of yet.

Other than those I can't think of independent tasks ATM. All of the TODOs on 
the list are more or less involved with package management components (building 
on top of and/or changing them). Maybe a few smaller independent tasks can be 
found (like writing an RPM spec parser in python), but I don't think there are 
many of those.

CU, Ingo

Other related posts: