From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7385 invoked by uid 1002); 7 Sep 2003 16:07: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 16355 invoked from network); 7 Sep 2003 16:07:18 -0000 From: Jan Krueger Organization: microgalaxy.net To: Gentoo-Dev Date: Sun, 7 Sep 2003 18:12:47 +0000 User-Agent: KMail/1.5.2 References: <1062944011.8455.118.camel@nosferatu.lan> <200309071645.10513.jk@microgalaxy.net> In-Reply-To: <200309071645.10513.jk@microgalaxy.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309071812.47423.jk@microgalaxy.net> Subject: [gentoo-dev] suggestion pkg_postinst X-Archives-Salt: 133b12bb-bd8c-4da0-babe-2e08288bbd3f X-Archives-Hash: 90be0421fac6dc1cc270335a8d3b95d6 As is i already mentioned in mail before i see pkg_postinst and collegues as a risk that makes the sandbox of portage pretty useless. I understand that after transfering an image to the life filesystem sometimes additional steps are required to make the software function well. If this tasks are very special, this task should be triggered manually (eg. via ebuild bla.ebuild config or such) It should be possible to preview what task this command would execeute. There is a variety of comman tasks that are triggered in pkg_postinst, like depmod -a or so. for these common things a secure abstraction should be available (an api similar to dodir and collegues). It must not be possible to modify the life filesystem from within an ebuild. (Maybe it would make sense to make this switchable, on or off. On - ebuilds can modify the life filesystem - for desktops Off - ebuilds can not modify the life filesystem - for those who care) Jan -- gentoo-dev@gentoo.org mailing list