Re: binary install details ...

2014-04-08 Thread Joshua Root
On 2014-4-8 22:58 , Clemens Lang wrote:
> Hey,
> 
>> The giving up isn't usually a problem because it only does that if the
>> archive is not available on packages.macports.org.
> 
> That might be the case for you, since you're close to packages.macports.org,
> but it isn't necessarily true for people in Europe like me.

Being close has nothing to do with it. If the archive is on p.m.o then
it will never give up until it downloads it (or exhausts the entire list
if p.m.o becomes unreachable after it starts).

>> sudo port archivefetch outdated && sudo port fetch outdated
> 
> That will fail on the first port without an archive, wouldn't it? You'd
> still need `-p` here.

It doesn't fail if you're not in binary-only mode.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: binary install details ...

2014-04-08 Thread Clemens Lang
Hey,

> The giving up isn't usually a problem because it only does that if the
> archive is not available on packages.macports.org.

That might be the case for you, since you're close to packages.macports.org,
but it isn't necessarily true for people in Europe like me.

> sudo port archivefetch outdated && sudo port fetch outdated

That will fail on the first port without an archive, wouldn't it? You'd
still need `-p` here.

-- 
Clemens Lang
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: binary install details ...

2014-04-08 Thread Joshua Root
On 2014-4-8 22:37 , Clemens Lang wrote:
> Hi,
> 
>> Unfortunately there's no easy way to say "fetch the archives for the
>> ports that have them, and the distfiles for those that don't."
> 
> You can use
>  $> sudo port -bp archivefetch $portlist
> to get all the binary archives available and ignore those that aren't.
> This is one of the few places where `-p` is not harmful. Adding `-b`
> might help in this case because it doesn't give up after three servers
> that don't have the binary archive.

The giving up isn't usually a problem because it only does that if the
archive is not available on packages.macports.org.

And actually, I forgot before that archivefetch does adjust the
statefile if it fetches an archive. So this should do the trick to fetch
everything you need to do an upgrade offline:

sudo port archivefetch outdated && sudo port fetch outdated

(the fetch will be a noop for ports that have an archive available).

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: binary install details ...

2014-04-08 Thread Clemens Lang
Hi,

> Unfortunately there's no easy way to say "fetch the archives for the
> ports that have them, and the distfiles for those that don't."

You can use
 $> sudo port -bp archivefetch $portlist
to get all the binary archives available and ignore those that aren't.
This is one of the few places where `-p` is not harmful. Adding `-b`
might help in this case because it doesn't give up after three servers
that don't have the binary archive.

-- 
Clemens Lang
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: binary install details ...

2014-04-07 Thread Joshua Root
On 2014-4-8 02:26 , Arno Hautala wrote:
> On Mon, Apr 7, 2014 at 12:03 PM, Peter Danecek  
> wrote:
>>
>> 2. Is there a way to "fetch" available binary packages, without installing 
>> the right away? There is the possibility do fetch all sources relevant for 
>> some port. Sometimes I would like to do something very similar with binary 
>> packages to install later when offline or on a pure internet connection. Is 
>> there a way to do this?
> 
> The command for this is "archivefetch". As in "port archivefetch
> ". I'd think you'd also be able to run something like: "port
> archivefetch  depof:", though I haven't tested that last
> one.

Unfortunately there's no easy way to say "fetch the archives for the
ports that have them, and the distfiles for those that don't."

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: binary install details ...

2014-04-07 Thread Joshua Root
On 2014-4-8 02:03 , Peter Danecek wrote:
> 
> Hi all,
> 
> I have some questions regarding binary installs. 
> 
> 1. I would like to know if there is some way to understand if a port was 
> installed from sources or from binaries. I'd assume this might be a 
> information which would have to go into the DB on activation, but is not 
> recorded (yet) ???

No. There isn't meant to be any practical difference in the archive you
end up with either way. And technically, all ports are built from source
and then installed from the resulting binary, just not necessarily on
the same machine.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: binary install details ...

2014-04-07 Thread Arno Hautala
On Mon, Apr 7, 2014 at 12:58 PM, Peter Danecek  wrote:
>
> Thanks for this hint. This is not yet documented in the man page, right? Or I 
> just missed it?
> ~petr

Yeah, I don't think it's documented anywhere. Maybe the man page? I
found out about it myself by asking on one of the mail lists a few
years back.

-- 
arno  s  hautala/-|   a...@alum.wpi.edu

pgp b2c9d448
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: binary install details ...

2014-04-07 Thread Arno Hautala
On Mon, Apr 7, 2014 at 12:03 PM, Peter Danecek  wrote:
>
> 2. Is there a way to "fetch" available binary packages, without installing 
> the right away? There is the possibility do fetch all sources relevant for 
> some port. Sometimes I would like to do something very similar with binary 
> packages to install later when offline or on a pure internet connection. Is 
> there a way to do this?

The command for this is "archivefetch". As in "port archivefetch
". I'd think you'd also be able to run something like: "port
archivefetch  depof:", though I haven't tested that last
one.

-- 
arno  s  hautala/-|   a...@alum.wpi.edu

pgp b2c9d448
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev