Re: Packages for Current ( 10.0 )
On Sat, Feb 18, 2012 at 12:11 PM, Mark Linimon lini...@lonesome.com wrote: On Fri, Feb 17, 2012 at 12:04:45AM -0500, Mehmet Erol Sanliturk wrote: I would be very happy I can contribute anything to development of FreeBSD . We are always happy to have help :-) If there appears an agenda of testing problems and explicit instructions how to apply tests , me and other persons may apply them and report the results . Well, there really isn't. There are some regression tests for src, but we have never established a framework to run them all automatically. Perhaps this is something you might be interested in? I am going to prepare a message like a specification for testing framework and send to you . In that framework , I want to adhere the current FreeBSD development ( web sites , available ports / packages , usability of existing testing facilities ) . I am planning to write the specification in such a structure that when a person takes it he/she will be able to generate an applicable project from it . This is not difficult for me because I was a computer science instructor in the University . In a message ( I do not remember its author's name ) it is said that there is no a farm of FreeBSD testing machines . I presume that's now for no? There are several sets. Here's how they are set up. - there is a src tinderbox which continually rebuilds the FreeBSD src tree, for various combinations of architectures and osreleases. (For src, the architectures can be cross-built.) These are intended to sanity-test that src is still buildable; in general the resulting binaries are not made available. - there is a clang buildbot whose purpose is to build FreeBSD src under clang continuously. - various people maintain ports tinderboxes. These are optimized for test-builds of one or at least a subset of the ports tree. In general the resulting binaries are not made available. - there is a new effort, Redports, to assemble a collection of ports tinderbox machines and make them available to interested people. We are actively working on this. - portmgr maintains the pointyhat cluster that do the package builds which are uploaded. These are optimized for building the entire ports tree in a secure fashion; the resulting binaries are made available. We are in the process of getting more machines online. - the pointyhat cluster is also used for -exp runs where portmgr regression-tests proposed changes to the overall ports tree to try to ensure as few regressions for large changes as possible. If we can generate such a testing ecological system , I think , FreeBSD development will benefit from it very much . I agree. But, for src, it's not something that I know much about, and will have to defer to others to comment. mcl At present , there a very valuable efforts for testing FreeBSD as you explained above . My approach will be not only testing the correctness of compilation but also execution correctness . As an example , when a snapshot is downloaded , installed and tried to boot , even it is NOT booting . My goal is to prevent such and other execution failures because every failure is a waste of very valuable human time and other resources . My primary profession ( university graduate subject ) is Mathematics/Statistics/Operations Research . During my undergraduate study I took also many electives from Industrial Engineering such as Motion and Time Study which its subject is to design work procedures that consumption ( such as time , energy , etc. ) is minimum while the outcome ( the amount of work performed , completed ) is maximum . From these points of view , I think , there are possibilities to improve development and wide adoption of FreeBSD which is a direct contribution to humanity welfare . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Packages for Current ( 10.0 )
On Fri, Feb 17, 2012 at 12:04:45AM -0500, Mehmet Erol Sanliturk wrote: I would be very happy I can contribute anything to development of FreeBSD . We are always happy to have help :-) If there appears an agenda of testing problems and explicit instructions how to apply tests , me and other persons may apply them and report the results . Well, there really isn't. There are some regression tests for src, but we have never established a framework to run them all automatically. Perhaps this is something you might be interested in? In a message ( I do not remember its author's name ) it is said that there is no a farm of FreeBSD testing machines . I presume that's now for no? There are several sets. Here's how they are set up. - there is a src tinderbox which continually rebuilds the FreeBSD src tree, for various combinations of architectures and osreleases. (For src, the architectures can be cross-built.) These are intended to sanity-test that src is still buildable; in general the resulting binaries are not made available. - there is a clang buildbot whose purpose is to build FreeBSD src under clang continuously. - various people maintain ports tinderboxes. These are optimized for test-builds of one or at least a subset of the ports tree. In general the resulting binaries are not made available. - there is a new effort, Redports, to assemble a collection of ports tinderbox machines and make them available to interested people. We are actively working on this. - portmgr maintains the pointyhat cluster that do the package builds which are uploaded. These are optimized for building the entire ports tree in a secure fashion; the resulting binaries are made available. We are in the process of getting more machines online. - the pointyhat cluster is also used for -exp runs where portmgr regression-tests proposed changes to the overall ports tree to try to ensure as few regressions for large changes as possible. If we can generate such a testing ecological system , I think , FreeBSD development will benefit from it very much . I agree. But, for src, it's not something that I know much about, and will have to defer to others to comment. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Packages for Current ( 10.0 )
The portmgr team has not yet started regular package builds for -current. We are working on re-allocating some resources to be able to do so. Note, however, that with -current being an early branch of a new major version, that the src that we are building against is changing rapidly. My personal recommendation would be that if you want prebuilt packages, you stay with -stable branches, unless you are particularly interested in helping to test the state of -current. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Packages for Current ( 10.0 )
On Thu, Feb 16, 2012 at 11:25 PM, Mark Linimon lini...@lonesome.com wrote: The portmgr team has not yet started regular package builds for -current. We are working on re-allocating some resources to be able to do so. Note, however, that with -current being an early branch of a new major version, that the src that we are building against is changing rapidly. My personal recommendation would be that if you want prebuilt packages, you stay with -stable branches, unless you are particularly interested in helping to test the state of -current. mcl I would be very happy I can contribute anything to development of FreeBSD . As I am always writing about importance of testing , in the same manner , I wish to test new developments to help to isolate problems , if I can . If there appears an agenda of testing problems and explicit instructions how to apply tests , me and other persons may apply them and report the results . In a message ( I do not remember its author's name ) it is said that there is no a farm of FreeBSD testing machines . If a web page is designed for testing with the goal and structure as described above it may be very useful and it may off load some tasks directly carried by the developers . Such a help will be very useful because the developers will be able to allocate more time to improve missing features . Please see my message for details : http://lists.freebsd.org/pipermail/freebsd-performance/2012-January/004536.html I have time and usable computer(s) for testing . I do not know FreeBSD internals very well . I can apply test(s) and report the results . I do not know very well scripting facilities of FreeBSD to design and implement such a testing web site pages and reporting by such scripts , but I can read and apply their instructions . I think that there will be many other volunteers to do such helps . If we can generate such a testing ecological system , I think , FreeBSD development will benefit from it very much . There is some need to include relevant facilities into FreeBSD supplied services , such as possibility of defining distinct monitors for stdin , stdout , stderr , besides serial consoles in loader.conf ; an easy facility to divert outputs of stdout and stderr into files to transmit them to testing site . Generation of XML files to obtain testing results directly processability by scripts , and other required modifications for testing applied promptly . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Packages for Current ( 10.0 )
Dear All , At present , ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-10-current/ is empty , and , http://pub.allbsd.org/FreeBSD-snapshots/ amd64 , head is prepared without ports.txz . To download a snapshot and test Current ( 10.0 ) , without ports seems to be not possible . Which ports can be used for Current ( 10.0 ) for X , Gnome , KDE , etc . ? Thank you very much . Mehmet Erol Sanliturk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
