Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] How automate source download from a google drive?
Date: Fri, 20 Feb 2015 08:33:32 +0200	[thread overview]
Message-ID: <20150220063332.GQ2937@tarshish> (raw)
In-Reply-To: <CAJpxd06ncFoxwLkeMyAuhPEXKNeH-Dh--Km=cvF0wN4e47xcVw@mail.gmail.com>

Hi Bryce,

On Thu, Feb 19, 2015 at 02:12:58PM -0800, Bryce Schober wrote:
> On Wed, Feb 18, 2015 at 5:55 PM, Steve Kenton <skenton@ou.edu> wrote:
> > This is a bit off the wall. I'm working with a package called tovid
> > which you download from a google drive by clicking on a link on the wiki
> > Darn if I can figure out how to put that into the .mk file to automate it.
> > Look through packages directory and did not see anything obviously like it
> >
> > Any thoughts would be appreciated
> 
> This worked:
> wget --no-check-certificate '
> https://docs.google.com/uc?export=download&id=0B7aAfFRdwkUmeGZTT2pua0d1Z2c'
> -O ~/Downloads/tovid.tar.gz
> 
> Based on this SO answer:
> http://unix.stackexchange.com/a/148674/22389
> 
> You'll need to specify the full download name of the file because the wget
> redirect apparently doesn't get it.

wget --content-disposition works for me, almost. I get 
'tovid-0.35.tar.gztovid-0.35.tar.gz'.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      parent reply	other threads:[~2015-02-20  6:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19  1:55 [Buildroot] How automate source download from a google drive? Steve Kenton
2015-02-19 22:12 ` Bryce Schober
2015-02-19 22:55   ` Steve Kenton
2015-02-20  6:33   ` Baruch Siach [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=20150220063332.GQ2937@tarshish \
    --to=baruch@tkos.co.il \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox