Am 14.01.2007 um 22:41 schrieb Christian Schaffner: [... some stuff by me talking about adding a nicer interface to the PDB ...]
> I like this idea very much and think that Fink would definitely > profit from an update of our pdb pages. Glad to hear that :-) > > One option I am missing on your browse.php right now would be the > selection of distributions (e.g. 10.4, 10.3 etc.). Would that be > possible? For example it would then be possible to check which > packages are not in stable for only the 10.4 tree. That definitely would be possible. In fact it would be easier than just showing all "stable" packages across all releases, I guess. Sidenote: Boy, the PDB is not really a "nice" example for a relational database... talking about e.g. orthogonalization (why is there a "fullname" field? Why do we hard code <p> in the "description" field? Why do we have a "release" field that mixes the values for "distribution/relase" with the tree (stable vs. unstable) ? Hrm, of course this is not he problem at hand, but I think it would make a lot of things easier if we fixed those issues. Might be quite a bit of work, though. > What I also would like: Show packages that could/should be moved to > the stable tree. The rule could be: > > 1) > Has the .info/.patch files of the package been changed in, say, the > last 2 weeks? > > 2) > Are all packages that this package depends on in the stable tree > (for that distribution)? "In stable" could mean any version that > satisfy the dependency, or, exactly the same version/revision than > in the unstable. I would suggest the latter definition, just to be > sure the package in the stable tree builds exactly as in the > unstable tree. > > If both conditions are met, the package could/should be moved to > the stable tree. Sounds like a nice idea, but ... > > Could browse.php deliver this information? ... this is not possible at this time, no -- the relevant information simply is not available in the DB. We could change that by adding a "last changed date" field, and a "deps fulfilled in stable?" field, though. That would require changes to the DB and the scripts used to generate and update it. And I wouldn't want to do any of these changes on the live system, so somebody would have to setup a test system for it, etc. > Anyhow, Max, I think the addition of browse.php would be great once > it is working correctly. Good. I think even in its current form (after temporarily disabling the not-quite-working parts, making the interface look a bit nicer, and adding some helpful text) it would be a good addition (replacement?) for the currently used interface. Bye, Max ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
