On 04/11/2005, at 8:04 PM, [EMAIL PROTECTED] wrote:
Packages become available for binaries when 1) They've been tested well enough that the maintainer feels that it can be moved to the stable source tree (with the guidance of other developers as required). 2) The package is not of a restrictive license, i.e. it is legal to distribute it as a binary. 3) A new Fink binary distribution is created.
Is there any way we could increase the frequency with which 3) is performed? I see hundreds of packages in -stable which have not had fresh binary versions for weeks and weeks.
Originally, I was under the impression that there was a machine autobuilding packages and uploading the binaries. However this is obviously untrue. Does the fink project have the resources to have such an autobuild system established? Ideally, packages would be built as .info files are committed, and so there wouldn't be too much of a massive load.
It would also help with testing.. there are many packages which are stale, simply because there is noone building them on a regular basis.
Regards, Phil., ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
