-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Hello ;)

First of all, thank you Max and Michael for getting back to me.

I realise that we cannot have fixed release cycles. We have talked about that on IRC and I see that there is no way to properly coordinate that. Yet I would appreciate it, if we could somewhat agree on a prioritised TODO list that is global. This means that someone who is interested in helping us with fink ( the package manager) can have a quick overview.
What is needed
Why is it needed
How badly is it needed and of course suggestions how it could be done.


Here is my first attempt at it. Please understand that these are my priorities and you have all the right in the world to put yours in as well.

GPG handling for info signing
Importance: Medium
How: There are Modules that can do OpenGPG in pure perl, but those have a lot of dependencies. This would mean that we should make gpg essential and maybe a Perl module that interfaces with it.



Move the package Index to a BerkDB
Importance: Medium
How: Store the relevant infos from the Info file in a BerkelyDB so that index searches are faster. This is especially interesting should we really expand past the 3000 package border by a significant number. how exactly, I have no idea.


Timestamp handling of Rsync Server
Importance: Very High
This is a blocker item. I cannot really go out there and acquire more Master mirrors or children until this system has been put in place. In short it means that fink checks which TIMESTAMP it received from the picked mirror it updated last from. If the TIMESTAMP for the mirror it contacted for the next update is older than the locally stored one, that mirror is skipped.
How: Hack support for that into Selfupdate.pm.


Add uidgui branch, automatic adding and removing or users/groups, phase out passwd file.
Priority: High
I have a few packages I would port, especially INN but I an not willing to deal with the passwd package.
How: Properly test the branches then merge them to HEAD



Add shlibs branch, automatic lib depends in deb files, use ${SHILB_LIBS} in the dep line and only hardcoding special cases or non libs.
Priority: Medium
I have no idea how this affects packaging, so I took the priority stated by Max.


Implement BuildDependsOnly right now it seems to be a switch that does nothing?
Priority: Low to Medium (yes, right now it's just a dummy field)
Same as above for this point.


Dependency engine
Priority: Medium to High
Probably a complete rewrite? This is definetly a long term goal?!

As you can see there is not much that has been added. maybe you could help me put this list into an order? Sorted by what is most important and should be done first? Personally I need that mirror stuff in as quickly as possible. Yes I know, people are busy, thus ia m patient and simply asking, but it is a perfect example of what _I_ would put on top

Your thoughts?

Thanks

- -d

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQE/ror+iW/Ta/pxHPQRA3s/AJ9wL102HJpBlTnhBV1JshkUx0+xFwCdGQmT
cyJVIEXXsoYov+U5NWVFtqc=
=m+Bu
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to