I think Victor would be very happy to have a single spec file that covers both the subset and full csound builds.... - Jim
On Mon, 2008-06-30 at 09:53 -0500, Dennis Gilmore wrote: > On Monday 30 June 2008, Jim Gettys wrote: > > Dennis: > > > > OLPC csound is an *exact* formal *subset* of full csound-5 built from > > the same sources as csound-5. > > > > It gets rid of tk/tcl dependency we don't want to carry in csound.... > > - Jim > There are much better ways to achieve that goal. than what was done. but > its > too late now. I'm working on defining some macros in totem right now so we > can always take the latest fedora spec, change some 0's to 1's and build a > much more minimalistic totem that's suitable for us. What is done is done > now. > > > On Sun, 2008-06-29 at 17:25 -0500, Dennis Gilmore wrote: > > > On Sunday 29 June 2008, Bert Freudenberg wrote: > > > > Am 30.06.2008 um 00:05 schrieb Dennis Gilmore: > > > > > On Sunday 29 June 2008, Bert Freudenberg wrote: > > > > >> I reanimated my script that shows differences between the latest > > > > >> joyride and candidate builds: > > > > >> > > > > >> http://dev.laptop.org/~bert/olpc3-joyride.html > > > > >> > > > > >> ... and in particular added a section to easily see what packages > > > > >> are in olpc3 and not in joyride, and vice versa. > > > > >> > > > > >> There are not only differences in package versions, but also in > > > > >> which packages are in. I wondered, for example, why csound is > > > > >> missing from joyride ... > > > > > > > > > > a second copy of csound landed in fedora as olpcsound. it is built > > > > > specifically for olpc and is in joyride. > > > > > > > > If it was named csound-olpc that would have been more obvious ... > > > > > > > > - Bert - > > > > > > Yes, first i heard of it was when i was asked to switch out csound and > > > csound- python for olpcsound. Had i been asked before hand i could have > > > suggested a way that the csound spec could have produced csound > > > csound-python and csound- olpc. but what is done is done. I personally > > > don't like anything being called olpc-foo, I think we should write code > > > that is useful outside of OLPC, useful to the whole world. In which case > > > the naming is really a poor choice. > > > > > > _______________________________________________ > > > Devel mailing list > > > Devel@lists.laptop.org > > > http://lists.laptop.org/listinfo/devel > > > _______________________________________________ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel -- Jim Gettys <[EMAIL PROTECTED]> One Laptop Per Child _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel