On 12/17/2012 07:46 PM, Anthony G. Basile wrote: >> >> 2. Write an ebuild for the project above, maintained in an overlay >> (also on GitHub), with sources fetched from GitHub. Add some small >> patch to configure.ac in the ebuild. Add USE flags. Add "make check" >> support to the build system, test with FEATURES=test. Many >> ebuild-related tasks can be easily added (e.g. installing init.d >> scripts). > > This would be totally new to them but I agree that's a good idea. I > don't know about GitHub. Can you delete projects from it when you're > done because I don't want to polute GitHub with lots of unpolished stuff.
You can. >> >> 3. Take an old-version ebuild for a project with a known bug, fetch >> the relevant git tag, and bisect to find the bug. Prepare a patch, >> describe patch submission process. > Hmm ... I didn't think of this but I could do that with the kernel on > virtual machines. You might want a userland program to avoid having to do reboots. I suppose git itself could be a good candidate for this. >> >> Wrt. subjects covered, will you cover sandboxing, installing to image >> vs. merging to live system, etc.? I would expect students to like such >> stuff. >> > At some point I would have to cover that. Like when I got over the > phases of emerging, stepping through them with ebuild. > You make me wish that this class was available when I was doing my undergraduate degree. I had to learn this on my own.
signature.asc
Description: OpenPGP digital signature
