Hi Chris, On Mon, May 4, 2015 at 11:53 PM, Chris Johns <chr...@rtems.org> wrote: > On 4/05/2015 9:00 pm, Hesham ALMatary wrote: >> On Mon, May 4, 2015 at 1:39 AM, Chris Johns <chr...@rtems.org> wrote: >>> On 4/05/2015 12:10 am, Hesham ALMatary wrote: >>>> On Fri, May 1, 2015 at 3:29 PM, Gedare Bloom <ged...@gwu.edu> wrote: >>>>> On Fri, May 1, 2015 at 4:36 AM, Hesham ALMatary >>>>> <heshamelmat...@gmail.com> wrote: >>>>>> On Fri, May 1, 2015 at 3:34 AM, Chris Johns <chr...@rtems.org> wrote: >>>>>>> On 1/05/2015 7:31 am, Hesham ALMatary wrote: >>>>>>>> +%source set binutils >>>>>>>> https://github.com/adapteva/epiphany-binutils-gdb/archive/epiphany-binutils-2.23-software-cache.zip >>>>>>>> +%source set gcc >>>>>>>> https://github.com/adapteva/epiphany-gcc/archive/epiphany-gcc-4.9.zip >>>>>>>> +%source set gdb >>>>>>>> https://github.com/adapteva/epiphany-binutils-gdb/archive/epiphany-gdb-7.8.zip >>>>>>> >>>>>>> Are these versions set or are they moving as the github repo moves ? >>>>>>> >>>>>> They are usually changing and modified, fixing bugs, add features, >>>>>> etc. My pull requests got merged to these branches. That's why I think >>>>>> hashes won't be practical. >>>>>> >>>>> Would it be better to pull the git repo itself to a certain commit >>>>> then? >>> >>> From a commit id, sure. If you can pull a zip file from a specific >>> commit id that would be better. >>> >> That's possible. >> >>> The reason we lock this down is to not changing anything on the user >>> until it is known to be stable. There are ways using user macros to >>> override the default and pick up the master branch for your testing so >>> you can test using the master branch and users pick up the last know >>> stable version. Contact me and I can explain if this is what you want. >>> >>>> For building tools we aim to have a reliable, reproducible tool >>>>> set. Dealing with "moving targets" makes it harder to support. >>>>> >>>> That's possible. The problem is that the current RSB doesn't support >>>> cloning from GitHub URLs like [1] or even [2]. [1] produce "malforned >>>> URL (no protocol prefix)", and [2] assumes that it's a .tar file, and >>>> doesn't even clone it. >>>> >>>> [1] g...@github.com:adapteva/epiphany-binutils-gdb.git >>> >>> Does git://g...@github.com/adapteva/epiphany-binutils-gdb.git work ? >>> >> Doesn't work. > > Ok. > >>>> [2] https://github.com/adapteva/epiphany-binutils-gdb.git >>> >>> The doco in this section https://docs.rtems.org/rsb/#_http_https_and_ftp >>> shows how to get a git version. Does this still work ? >>> >> The problem with cloning from github is that the URL should be >> prefixed with "git://", and this is not the case for github repos. I >> think download.py should be hacked to enable it. > > Yes I tend to agree. > >> Anyway, I'll submit a patch that downloads from specific commits. > > Thanks. > I case you didn't notice, I submitted 2 patches: 1/2 is sent separately, and 2/2 got merged with this e-mail thread (don't know why), it's two replies above this reply. > Chris
-- Hesham _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
