Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Aug 2002 10:39:37 -0400
From:      Antoine Beaupre <anarcat@anarcat.ath.cx>
To:        candelabrum@canada.com
Cc:        libh@FreeBSD.org
Subject:   TODO refresh (was: volunteer)
Message-ID:  <D2D3AF16-B05C-11D6-BD5C-0050E4A0BB3F@anarcat.ath.cx>
In-Reply-To: <20020815063546.21799.h008.c009.wm@mail.canada.com.criticalpath.net>

next in thread | previous in thread | raw e-mail | index | archive | help
BTW: I'll put this up on the web. Each time I re-inspect what needs to=20=

be done with libh, I come up with new stuff ;)

On Thursday, August 15, 2002, at 09:35 AM, candelabrum@canada.com wrote:

> Hi,
> Any direction is acceptable. I think that you know
> project's priorities better. I am rolling the latest
> snapshot in my box and after I=92ll can to see the
> details. Generally I am interested in writing the
> package engine or the user interface or something else.
> It would be better if somebody let me know about
> appropriate directions for beginning work.

Well, the package engine and the user interface is pretty much all there=20=

is to libh. :)

Both engines need a rewrite, in part or in full.

Hui
=3D=3D=3D

Max is currently engineering a pretty throughout Hui (libH User=20
Interface) rewrite, and he's going pretty well on this side.

I've been thinking about this, and we will need new widgets once this is=20=

done.

- a tree widget
- an image widget (that will show nothing in tvision :)
- a general "canvas" scrollable widget that can hold other widgets

Also, the listbox widget needs to be able to sort its entries and=20
possibly move its columns around.

Max will probably be better than me to instruct you on what there is to=20=

do.

Package System
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The package API is at its infancy. You can find it at=20
http://usw4.freebsd.org/~libh/sysinstall2/ . As I said, it is far from=20=

complete, and not detailed enough yet. I have tried to make it clearer,=20=

but it's an evergoing task.

It would be interesting to make this document look more like an API.=20
Right now, it's mostly a libh design document. But it still gives a good=20=

idea of how libh is made and what it should be able to do.

On the implementation side itself, there is a strong need of finishing=20=

the basic implementation that was started. Right now, packages can be=20
generated and installed, but dependencies, uninstalls and plenty of=20
other very interesting libh functions are non-working or =
non-implemented.

This needs to be done.

I don't exactly know what's missing and where. I got interested in the=20=

package system only recently, and there's very few documentation. So=20
another task is to analyze the code and the documentation to see where=20=

we're at. Gettting a simple list of what works and what doesn't would be=20=

really great, and setting up regression tests would be extraordinarly=20
helpful.

 =46rom what I understand now, the libh package system is really zip and=20=

DB3 based. The class hierarchy doesn't allow much flexibility on this=20
side, so it would be a good thing to start isolating the implementation=20=

(eg. Zip file) from the concept (eg. Archive or Package) in the code=20
itself. Also, inline class and function documentation is seriously=20
lacking. We now have the tools to extract that documentation (Doxygen),=20=

so we need to document the whole thing.

So in short, here are the package tasks:

- finish package API
- figure out what is and what needs to be implemented
- implement missing parts to get a viable package system
- document the whole package system via Doxygen
- isolate the package system formats (database and package format sides)=20=

in seperate classes
- setup regression tests

Choose your task, work on the tree to get accustomed to it and send us=20=

patches! I'll be very glad to review those and commit them to the tree=20=

if they're ok. :)

> I can=92t send mail to mail-list direct from my local
> computer, there isn=92t any error message. I remember
> there was strong position with reverse DNS, does it
> matter now?

hub.freebsd.org refuses messages coming from computers without reverse=20=

DNS mappings or with reverse mappings not matching the pretended=20
hostname (IIRC).

A.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-libh" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D2D3AF16-B05C-11D6-BD5C-0050E4A0BB3F>