Displaying 3 results from an estimated 3 matches for "extunix".
Did you mean:
extenip
2013 Dec 12
0
xen-api-libs REMOVED from testing
...in testing)
Hint: <http://release.debian.org/britney/hints/mehdi>
# 10-12-2013; generated with comigrate -c /srv/release.debian.org/britney/code/b2/britney.conf --migrate ocaml --remove xen-api-libs --remove otags --remove ocamlduce --remove jocaml --remove ocaml-sqlexpr --remove ocaml-extunix --remove obrowser --remove janest-core --remove galax --remove cduce --remove cameleon --remove sks --remove approx
The script that generates this mail tries to extract removal
reasons from comments in the britney hint files. Those comments
were not originally meant to be machine readable, so if t...
2014 Mar 10
2
[PATCH] builder: complete architecture handling
Add the possibility to choose which architecture use to build the wanted
image (--arch). Since this implies that running commands on the guest is
usually not possible when the architecture is different than the host
one, another new option (--allow-foreign-arch-ops) allows to run
commands nevertheless.
The caching scheme is adapted to account for the architecture (with
--print-cache showing the
2014 Mar 11
4
Re: [PATCH] builder: complete architecture handling
...a/builder/uname-c.c b/builder/uname-c.c
>
> I would have just done:
>
> List.hd (external_command "uname -m")
>
> but now you've written the FFI code, that's fine :-)
I'm starting to think that in the next stable series (say 1.27/1.28) we
could require ExtUnix, and get rid of the FFI codes we currently have
(setlocale, fsync, mkdtemp, statvfs, and now uname).
--
Pino Toscano