gnu-linux-libre
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU-linux-libre] Uruk GNU/Linux evaluation


From: Ali Abdul Ghani
Subject: Re: [GNU-linux-libre] Uruk GNU/Linux evaluation
Date: Tue, 28 Jun 2016 02:05:10 -0700

> I think you should at least make a sha256 checksum of all the scripts
> you are running and the assets you are installing.
now we use git
in git
if the  Connection is stop
  git will Tell the user
and  Nothing will be install



2016-06-28 1:42 جرينتش-07:00, hellekin <address@hidden>:
> On 06/27/2016 01:43 PM, Jaromil wrote:
>>
>> I believe that Uruk can be 100% free even without offering a whole
>> package repository, but just by publishing all sources
>>
>
> I tend to agree with Jaromil (not only because we're brothers) that
> having your own repositories is the cherry on top of the cake.
>
> I understand that the "own repos" rule is to prevent anyone from making
> a distro out of another without core changes (why not participate in the
> original distribution directly?).
>
> Nevertheless I see Ali's case a bit differently than what the rule
> suggests: the source for Uruk is already 100% free Trisquel, so the
> argument that the developers should be able to patch things themselves
> seems a be redundant if not plain irrelevant;  Ali's work for software
> freedom, accessibility, and growing community support around these has
> been exemplary.  Not only he volunteered across free distros to
> facilitate the adoption of accessible software, he also brings together
> people locally in war-torn Iraq.
>
> For these reasons, the "no own repos" rule should be circumvented
> somehow.  That could mean to work with Trisquel to integrate changes
> made in Uruk, or financial support to bring the Uruk team to capacity.
>
> In any case, judging on absolute values is not gonna work.
>
> ==
> hk
>
>
>


-- 
Emacs is the ground. We run around and act silly on top of it, and
when we die, may our remnants grace its ongoing incrementation.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]