Re: [Fink-devel] Begining of a fink "roadmap", this is just an overview draft

[Max Horn]

Am Samstag, 08.11.03 um 13:54 Uhr schrieb Darian Lanx:

[...]
Let us assume we are planning the next 5 releases with a release
interval of 3 weeks? Or is that something we cannot achive?
I think we shouldn't do this. At least I see no real gain from it, and 
most of the Fink developers may have a hard time commiting to such 
strict time schedules. Just my two cents <shrug>.


- -d

David:
GPG handling for info signing and/or deb signing
Might be nice if done correctly.

Proper handling of our Mirror system, reading and working with the now 
supplied TIMESTAMP
Not sure what that exactly means...

Moving the Index to something like a berkelyDB
Priority: Low; Difficulty: Medium to Hard (I still have to see even a 
proof of concept of this...)

Integrate something like the package-contest into fink, so that one 
would do
Priority: Very Low

On the cli fink report
What does this mean?


Justin:
Add uidgui branch, automatic adding and removing or users/groups, 
phase out passwd file.
Priority: Medium to High

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

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)


Benjamin
- - move fix-fink into a "fink lint" option
Not happy with that name. "lint" traditionally is a tool which performs 
strict syntax checking on C source code. As such it corresponds to our 
package validator.
fix-fink, on the other hand, updates/rebuilds packages if it detects 
that they are linking against old/outdated libraries (right now, 
libSystem and libpng are covered). As such, the name "fink-fix" is 
really describing it well.
Anyway, any particular reason why you think it should be in fink, 
instead of remaining a separate package? I see none.


- - clean up the dependency engine
Hah, yeah, right. An rewrite it to do all sorts of new features =)
Priority: Medium to High
- - make fink capable of checking apt to resolve dependencies (ie, if
   a binary that's not been downloaded meets the requirements, download
   instead of building)
Priority: Low, Difficulty: Nasty (it will basically add even more 
clutter, complications and special cases to consider inside the 
dependency engine). The UI issues & implication are not to be 
underestimated, too.



Cheers,

Max



-------------------------------------------------------
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