[PATCH v2 04/10] user: Add "Obtain the Sources" section

Joel Sherrill joel at rtems.org
Tue Feb 12 20:41:42 UTC 2019


On Tue, Feb 12, 2019 at 12:18 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> On 12/02/2019 03:48, Chris Johns wrote:
> >> We chose
> >> +:file:`$HOME/quick-start/rtems/5` as the installation prefix.
> >> +
> >> +You need at least two source archives or Git repositories to work with
> RTEMS.
> >> +You can download the source archives for a released RTEMS version or
> you can
> >> +clone Git repositories to get all versions of RTEMS including the
> development
> >> +head.
> >> +
> >> +We will clone the Git repositories into :file:`$HOME/quick-start/src`.
> >> +
> >> +.. code-block:: none
> >> +
> >> +    mkdir -p $HOME/quick-start/src
> >> +    cd $HOME/quick-start/src
> >> +    git clonehttps://git.rtems.git/rtems-source-builder  rsb
> >> +    git clonehttps://git.rtems.git/rtems
> > I feel we need the https access to git fixed for this to be in the doco.
> I have
> > no idea how to sort this out. We have and are supporting git:// so may
> be this
> > should be documented and the alternative added as helper for those who
> cannot to
> > git via the git protocol?
>
> We should fix our HTTPS clone support or use Github as the default
> source for read-only clones.


Is there a ticket for supporting https clones?


> From my point of view offering the Git
> protocol is user unfriendly. The clone via HTTPS works everywhere, even
> behind firewalls and proxies.
>

Perhaps a word is missing in your response.

Some have to use https and we should support it. I wouldn't recommend it
as a first choice. If someone doesn't have to use it, then they should use
the
native git protocol.

--joel


>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190212/5fd442c6/attachment-0002.html>


More information about the devel mailing list