From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24997 invoked by uid 1002); 7 Sep 2003 19:38:18 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 20535 invoked from network); 7 Sep 2003 19:38:18 -0000 From: Jan Krueger Organization: microgalaxy.net To: azarah@gentoo.org Date: Sun, 7 Sep 2003 21:36:23 +0000 User-Agent: KMail/1.5.2 Cc: Thomas de Grenier de Latour , Gentoo-Dev References: <200309071955.39319.jk@microgalaxy.net> <1062959282.8455.151.camel@nosferatu.lan> In-Reply-To: <1062959282.8455.151.camel@nosferatu.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309072136.23416.jk@microgalaxy.net> Subject: Re: [gentoo-dev] Some suggestions X-Archives-Salt: 3a8ca18a-f987-4054-be8b-d148a5e71e8e X-Archives-Hash: f8d7578c00cd4548c802953ec382d306 On Sunday 07 September 2003 18:28, Martin Schlemmer wrote: > Ok, but .rpm/.deb have the same kind of flaws ... Absolutly correct. Thats why i dont use them. > From here on I can > only see that you can use LFS or such, that you can make sure everything > is ok. > > PS: How are you going to verify that gcc's cvs repo was not > compromised? Thats very realistic and compromise of at least the gnu ftp server happened not so long ago. I see the FSF to be responsible for handling this. > Or the kernel's ? Thats the responsibility of kernel.org. gentoo is responsible for portage and what portage does. Thats what i would like to discuss here. > I guess you are going to > start coding you own kernel, tool-chain and the rest even > sooner now that we know how flawed linux, gnuish apps, etc > are. :) alternatives there are, so many of them, i just have to choose and i already did. No need for me to write my own os :) -- gentoo-dev@gentoo.org mailing list