At this point I think we should not make any changes in how we support i686.
Graham
On Thu, Jan 26, 2017 at 7:37 AM Graham Christensen
wrote:
>
> As far as I know, Nix has no way to gather statistics on how many people
> are using different architectures. This makes
Please don't drop it yet :-)
% uname -a
Linux schleppa 4.4.40 #1-NixOS SMP Fri Jan 6 10:16:31 UTC 2017 i686
GNU/Linux
Thank you,
Tilo
--
Best regards / Viele Grüße,
Tilo Schwarz
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
Am 26.01.2017 um 14:37 schrieb graham at grahamc.com (Graham Christensen):
> anyone on this list know anyone
> using NixOS on i686?
Hi, we're currently moving from openSUSE to NixOS.
More than half of the machines I'm administering
are i686 architecture, and 32 bit support
is is one of many
2017-01-27 14:13 GMT+01:00 Eelco Dolstra :
>
> I think it's more an issue of build time, especially if we want Hydra to
> build
> PRs (which could trigger a full rebuild in the worst case).
>
>
I think we could/should use a GitHub bot like the @bors used by the Rust
On 01/27/2017 02:13 PM, Eelco Dolstra wrote:
> Another possibility is to reduce the number of packages that get built for
> i686,
> but it would be tricky to decide which packages to keep.
I had thought of building i686 packages "less often", but I couldn't see
an easy way to do that, except
I use nixos i686 on virtualbox, xen and on some old hardware.
For some applications, i686 binaries require less memory and are
slightly faster.
From my personal use, the dismiss of support of i686 would be a loss.
Marco
2017-01-26 16:46 GMT+01:00 Ryan Trinkle :
> I provide
On Thu, Jan 26, 2017 at 08:37:06AM -0500, Graham Christensen wrote:
> One person on IRC said they think they may have used it once. Does
> anyone on this list use NixOS on i686? anyone on this list know anyone
> using NixOS on i686?
I use a IBM ThinkPad T43 with NixOS.
Vladimír Čunát writes:
> When creating a new stable, I think the month between branch-off and
> release should be enough to fix any important i686-specific issues, as
> they tend to be relatively rare.
However then, in the worst case, we're left to git-bisect 6 months of
I think the main resource cost for us is the build farm and binary
cache. Idea: what about building full i686-linux set only on stable
branches?
Note: obviously, callPackage_i686 will still use i686 even if "evaluated
for x86_64", which is what we want for wine, skype, etc.
When creating a new
> As far as I know, Nix has no way to gather statistics on how many people
> are using different architectures. This makes questions like this a bit
> awkward.
>
> One person on IRC said they think they may have used it once. Does
> anyone on this list use NixOS on i686? anyone on this list know
I provide i686 binaries for users of reflex-platform, a nix-based
environment for developing GUI applications in Haskell. I have only a few
confirmed users of i686, but since their machines are correspondingly older
and less powerful than most of my other users', the benefit of nix's binary
On 17-01-26 08:37am, Graham Christensen wrote:
> One person on IRC said they think they may have used it once. Does
> anyone on this list use NixOS on i686? anyone on this list know anyone
> using NixOS on i686?
I’m using it for one old machine running the audio server
of our hackerspace.
--
It would be a pity if we didn't support i686 anymore.
I use NixOS on a NAS, which only supports i686.
This question has been asked before (about 6 months ago).
On Thu, Jan 26, 2017, 15:02 Benno Fünfstück
wrote:
> There's still a few packages in nixpkgs that
There's still a few packages in nixpkgs that require i686, like Skype, even
on x86_64.
Benno
Graham Christensen schrieb am Do., 26. Jan. 2017,
14:37:
>
> As far as I know, Nix has no way to gather statistics on how many people
> are using different architectures. This makes
> Does anyone on this list use NixOS on i686?
Besides some VirtualBox image laying around I have one physical machine:
$ uname -a
Linux kappa 4.4.31 #1-NixOS SMP Thu Nov 10 15:37:00 UTC 2016 i686
GNU/Linux
$ grep 'model name' /proc/cpuinfo
model name: Mobile Intel(R) Pentium(R) III
15 matches
Mail list logo