-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I noticed the following:
1. Buildfarm trunk build fails over and over again.
2. The only two packages from build-for-release that fail are updated
Gnash packages.
3. The real build failure is DejaG
> Hmm, why would you want to mark software like that? For example, if I as
> a user want to install Skype, I just want to have it installed. What use
> is it for me if the system first says: "Sorry, Dave, can't do that. You
> first need to sign with your blood that you are not a true open source
>
Hi,
Eelco Dolstra <[EMAIL PROTECTED]>
writes:
> I don't think I would like separating the Nix expressions for non-free
> packages
> from Nixpkgs, since that would make live more difficult for users who do want
> to
> use a non-free package (say the NVIDIA driver), but it would be a good idea
>
Hello,
Arie Middelkoop <[EMAIL PROTECTED]> writes:
> Ludovic Courtès wrote:
>> Currently, Nixpkgs contains a fair amount of non-free software, some of
>> which gets installed by default. I would personally like it if we would
>> gradually separate non-free software from free software in Nixpkgs
Hi,
Daniel Clark wrote:
> I'm in the process of seeing how hard it would be to port NixOS to
> non-intel architectures / boot loaders other than grub. Specifically
> I'm working with a Loongson 2f machine, which is a mipsel64 (64-bit
> MIPS little-endian) machine that uses the PMON 2000 boot load
hi Daniel,
> I'm in the process of seeing how hard it would be to port NixOS to
> non-intel architectures / boot loaders other than grub. Specifically
> I'm working with a Loongson 2f machine, which is a mipsel64 (64-bit
> MIPS little-endian) machine that uses the PMON 2000 boot loader.
If you ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arie Middelkoop wrote:
>> Currently, Nixpkgs contains a fair amount of non-free software, some of
>> which gets installed by default. I would personally like it if we would
>> gradually separate non-free software from free software in Nixpkgs, so
>> t
Ludovic Courtès wrote:
> Hello,
>
> "Daniel Clark" <[EMAIL PROTECTED]> writes:
>
>> I'd also like to know if there is any interest amongst the NixOS
>> developers to make NixOS a distribution that would be compliant with
>> the FSF/GNU Project's Guidelines for Free System Distributions [1] and
>>
Hi,
Michael Raskin <[EMAIL PROTECTED]> writes:
> Ludovic Courtès wrote:
>> The problem is with directories (info "(texinfo)Installing Dir
>> Entries"). Directories show the list of available manuals when running
>> `info' (or `C-h i' in Emacs) with no arguments.
>>
>> Conversely, accessing a sp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludovic Courtès wrote:
> The problem is with directories (info "(texinfo)Installing Dir
> Entries"). Directories show the list of available manuals when running
> `info' (or `C-h i' in Emacs) with no arguments.
>
> Conversely, accessing a specific ma
Hello,
"Daniel Clark" <[EMAIL PROTECTED]> writes:
> I'd also like to know if there is any interest amongst the NixOS
> developers to make NixOS a distribution that would be compliant with
> the FSF/GNU Project's Guidelines for Free System Distributions [1] and
> thus recommendable by the Free Sof
Hi,
"Andres Loeh" <[EMAIL PROTECTED]>
writes:
> Actually, this is another argument against hooks. The system environment
> can change without user action, so ideally all "effects" of such a change
> should be immediate, and not require user action either. On the other hand,
> we know the path of
12 matches
Mail list logo
