From: Denys Dmytriyenko <denys@ti.com>
To: Jacob Stiffler <j-stiffler@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [PATCH] arago.conf: add TI_MIRROR to mirrors
Date: Thu, 15 Feb 2018 13:09:43 -0500 [thread overview]
Message-ID: <20180215180943.GT31854@edge> (raw)
In-Reply-To: <1518716270-17171-1-git-send-email-j-stiffler@ti.com>
Thanks!
On Thu, Feb 15, 2018 at 12:37:50PM -0500, Jacob Stiffler wrote:
> * Add the TI_MIRROR as a fallback to any upstream fetch issues.
>
> Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> ---
> meta-arago-distro/conf/distro/arago.conf | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/meta-arago-distro/conf/distro/arago.conf b/meta-arago-distro/conf/distro/arago.conf
> index 00db445..bc7c18c 100644
> --- a/meta-arago-distro/conf/distro/arago.conf
> +++ b/meta-arago-distro/conf/distro/arago.conf
> @@ -7,9 +7,21 @@ FEEDURIPREFIX ?= "packages/${DISTRO}-morty/${BUILD_VARIANT}/"
>
> OPKG_ARGS_remove = "--prefer-arch-to-version"
>
> +TI_MIRROR = "http://software-dl.ti.com/processor-sdk-mirror/sources/"
> MIRRORS += " \
> ftp://.*/.* http://arago-project.org/files/sources/ \n \
> https?$://.*/.* http://arago-project.org/files/sources/ \n \
> +bzr://.*/.* ${TI_MIRROR} \n \
> +cvs://.*/.* ${TI_MIRROR} \n \
> +git://.*/.* ${TI_MIRROR} \n \
> +gitsm://.*/.* ${TI_MIRROR} \n \
> +hg://.*/.* ${TI_MIRROR} \n \
> +osc://.*/.* ${TI_MIRROR} \n \
> +p4://.*/.* ${TI_MIRROR} \n \
> +npm://.*/.* ${TI_MIRROR} \n \
> +ftp://.*/.* ${TI_MIRROR} \n \
> +https?$://.*/.* ${TI_MIRROR} \n \
> +svn://.*/.* ${TI_MIRROR} \n \
> "
>
> # SDK paths and names
> --
> 2.7.4
>
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
prev parent reply other threads:[~2018-02-15 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 17:37 [PATCH] arago.conf: add TI_MIRROR to mirrors Jacob Stiffler
2018-02-15 18:09 ` Denys Dmytriyenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180215180943.GT31854@edge \
--to=denys@ti.com \
--cc=j-stiffler@ti.com \
--cc=meta-arago@arago-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.