Stuart - I've uploaded a small change that I'm calling rc5. This builds a more recent kernel with RPi patches obtained from http://github.com/raspberrypi/linux than the one I had been using.
I have not modified the core code to get a tarball or RPM from an arbitrary URL yet as I'm not sure that's the direction you want to go. If you are still planning on merging my changes into the repository this weekend, I would be fine with you adding a README.RPI file directing the users to download the toolchain from https://github.com/downloads/midnightyell/RPi-LTIB/raspberrypi-tools-9c3d7b6-1.i386.rpm instead of it coming from the gpp. Please let me know if you have any questions. As usual, my packages, diffs, etc. may be found here: https://drive.google.com/#folders/0B5oPSqrs5WbUNndYZ0pxTm10NkE Rob Bishop - one of the RPi designers - is in town Saturday, and I'm signed up to talk about what I've done with LTIB for the Pi after his speech. I plan on saying that the PI will be supported in the LTIB trunk "shortly". I'm looking forward to it :) On Thu, Oct 4, 2012 at 1:58 PM, Sean Malloy <[email protected]> wrote: > I think the best thing to do is to add a mechanism to LTIB so that you can >> specify a direct download URL for the toolchain. >> > > I have uploaded the toolchain RPM to > https://github.com/downloads/midnightyell/RPi-LTIB/raspberrypi-tools-9c3d7b6-1.i386.rpm > > Personally, I'm fond of the idea of anytime LTIB sees a Source: link in a > spec file that starts with http[s]://, it should attempt a wget on the URL > if the file is not found in the gpp, lpp, or ldirs. > > That would solve this problem nicely. > > Objections? > > -- > Sean C. Malloy > [email protected] > > -- Sean C. Malloy [email protected]
_______________________________________________ LTIB home page: http://ltib.org Ltib mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/ltib
