Re: Armv6l vs armv7l

Thomas Leonard <[email protected]> Sat, 1 Apr 2017 13:09:33 +0100
Newsgroups gmane.comp.file-systems.zero-install.devel
Message-ID <CAG4opy8JMApHb3=RBWjTP=Lk78QDFEErkKTyJgN72-EOzCQS_w@mail.gmail.com>
On 31 March 2017 at 02:33, Eric Duhamel <[email protected]> wrote:
>
>
> On March 29, 2017 11:01:35 AM PDT, Thomas Leonard <[email protected]> wrote:
>>
>>The compatibility table is here:
>>
>>https://github.com/0install/0install/blob/master/ocaml/zeroinstall/arch.ml#L63
>>
>>However, it looks like the armv6l -> armv7l line was added in Nov
>>2014, after 2.7 was released:
>>
>>https://github.com/0install/0install/blob/master/ocaml/zeroinstall/arch.ml#L63
>>
>>0install 2.9 would be the first version to support that. You can try
>>it like this:
>>
>>$ 0install add 00install http://0install.net/tools/0install.xml
>>$ 00install select --cpu=armv7l http://repo.roscidus.com/python/python
>>- URI: http://repo.roscidus.com/python/python
>>  Version: 3.4.2-2
>>  Path: (package:deb:python3:3.4.2-2:armv6l)
>
> Thanks. Looks like 0install add can't select a proper version of GnuPG when adding 0install.xml though, due to != armv7l again.

Oh. What about if you ask for a specific CPU type, e.g.

0install add 00install http://0install.net/tools/0install.xml --cpu=armv6l

> For python and gnupg, wouldn't 0install normally select the package that is present on my system instead of a remote feed?

Yes, it should do. What OS are you using? If you have the GUI, you can
right-click on the package version and choose "Explain this decision"
from the menu to find out why it didn't use it.


-- 
talex5 (GitHub/Twitter)        http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D  6A51 7513 3C8F 94F6 E0CC

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot