From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21047 invoked from network); 1 Dec 2004 20:51:20 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 1 Dec 2004 20:51:20 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1CZbRX-0001fL-QA for arch-gentoo-portage-dev@lists.gentoo.org; Wed, 01 Dec 2004 20:51:19 +0000 Received: (qmail 29215 invoked by uid 89); 1 Dec 2004 20:51:18 +0000 Mailing-List: contact gentoo-portage-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-portage-dev@lists.gentoo.org X-BeenThere: gentoo-portage-dev@gentoo.org Received: (qmail 16789 invoked from network); 1 Dec 2004 20:51:16 +0000 Date: Wed, 1 Dec 2004 21:51:10 +0100 From: Alpt To: gentoo-portage-dev@lists.gentoo.org Message-ID: <20041201205110.GA10518@nihil> References: <20041201175509.GA32317@darkalpt> <200412011922.56841.luke-jr@utopios.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412011922.56841.luke-jr@utopios.org> User-Agent: Mutt/1.4.2.1i User-Agent: hahaSRY Subject: Re: [gentoo-portage-dev] The merge of emerde with emerge X-Archives-Salt: da34a349-a41b-40af-b1ff-273d2aeed0b6 X-Archives-Hash: 9068bf52714f71d9ad24dcd1f72dae0e On Wed, Dec 01, 2004 at 07:22:56PM +0000, Luke-Jr after a spiritual call wrote : ~> On Wednesday 01 December 2004 5:55 pm, Alpt wrote: ~> > For those who don't know the story: ~> > Emerde is born on Septmber 2003. It is a port of the portage for ~> > slackware or generic distro. ( http://emerde.freaknet.org ) ~> ~> This doesn't make sense to me... Portage is universal enough to work on any ~> other common Linux system... okey, install it in slackware then and use it. let me see please. ~> > In the while I've added various handy features. ~> > These are the additional features added in emerde: ~> > tgz support: A tgzfile must be a Slackware pkg. Emerde will resolve the ~> > tgz's dependences and will install it. ~> ~> Shouldn't be part of Portage. Portage handles ebuilds, not Slackware packages. It is to let emerde live peacefull in Slackware. ~> > pfile: Emerde will apply the specified action to all the packages listed ~> > in the pfile ~> ~> emerge $(cat pfile) emerde pfile pfile ;) ~> > invulnerable: Updates all the packages which have suid binaries. ~> ~> What is the purpose behind this? Some kind of bad idea to assume that suid ~> packages are the only ones with security holes and updates are solely to fix ~> them? no, obviously it isn't vital but it is usefull in some cases. ~> > maketgz: Emerde will build Slackware's tgz packages for all ebuilds ~> ~> A better idea would be to convert GRPs to Slackware tgz Slackware compatibility dude. ~> > skipit: Emerde allows you to skip to the next merge with the SIGINT signal ~> > or by pressing CTRL+c. ~> ~> There's usually an order for a reason. Usually, when I press Ctrl-C, I want ~> emerge to stop altogether. Yep, but let's assume we are doing "emerde pfile pfile" or in your case "emerde `pfile`". If you want to skip the current merging you have to stop emerge, modify the pfile and again "emerde pfile pfile". It isn't very pretty when you have a list of 50 pkgs and you are arrived at 50% in the list and you are _not_ doing --update. ~> > Compilation resume: ~> > Emerde resumes an interrupted or aborted compilation without rebuild ~> > the pkg and restart the compilation. ~> ~> Portage already does this for me. no, if halt the compilation and the next time ./configure will be runned so you'll start the compilation again. ~> > LAN-sync: The syncing of the portage can be done using another machine that ~> > had already done it. See ACTION:sync in the emerge(1) man page. ~> ~> See SYNC in /etc/make.conf.example LAN-sync is: rsync -e mymachine:/usr/portage/ /usr/portage/ you can't do it right now... ~> > --searchcontents: ~> qpkg /path/to/file, no? emerde -N /path/to/file, no? ~> > buildworld: Rebuilds or updates the "world" file (/var/cache/edb/world) ~> ~> There's scripts to do this, though these will always be inaccurate hacks, ~> since you cannot really rebuild the world file. okey. ~> > por2pkg: por2pkg converts entries in the portage's db to Slack's db ~> > entries. pkg2por: pkg2por converts entries in the Slack's db to portage's ~> > db entries. pordbcheck: Checks if the programs listed in the portage's db ~> > are really installed. ~> ~> Doesn't belong in a package manager. Slack compat. ~> > initd-cfg: /etc/init.d editor. ~> ~> Doesn't belong in a package manager. you are managing the init.d files of the packages installed with the package manager ~> Portage is already distro-independent... The only distros to have considered ~> using it (Zynot and Utopios) both determined that it would be better to write ~> a better package manager based on the ideas. Install it in the other distro then. Did you considered for example baselayout? regards -- :wq! "I don't know nothing" The One Who reached the Thinking Matter '.' [ Alpt --- Freaknet Medialab ] [ GPG Key ID 441CF0EE ] [ Key fingerprint = 8B02 26E8 831A 7BB9 81A9 5277 BFF8 037E 441C F0EE ] -- gentoo-portage-dev@gentoo.org mailing list