public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Will Rogers" <wjr@wam.umd.edu>
To: <gentoo-dev@cvs.gentoo.org>
Subject: RE: [gentoo-dev] An Offering:  the EMerge Interface
Date: Wed Aug 22 00:00:02 2001	[thread overview]
Message-ID: <000301c12acf$9a904eb0$0801a8c0@saucer> (raw)
In-Reply-To: <20010821202433.B20174@prosalg.no>

Karl,

I rewrote the entire thing in Python (partly to see if I could).  I
haven't tested it as much as the original because it's 2am and I have to
be at work in seven hours, but I was able to merge and unmerge joe, as
well as query a bunch of stuff, without any trouble on my system.  It is
at present a lot slower than the Perl version because I used
os.path.walk instead of opening a pipe from find, but I'll probably
change that given the horrid performance it causes.

I send this directly to you because I get the faint impression that
gentoo-dev is not the correct place to send this sort of thing and I
didn't want to nag anyone without some guidance ;)

The new version is posted at http://www.wam.umd.edu/~wjr, but as you can
see I consider it a beta (more because of performance than stability--it
takes several seconds to execute a dependency check with around 8
dependencies).

Will Rogers, going to sleep.
wjr@wam.umd.edu


> -----Original Message-----
> From: gentoo-dev-admin@cvs.gentoo.org 
> [mailto:gentoo-dev-admin@cvs.gentoo.org] On Behalf Of Karl 
> Trygve Kalleberg
> Sent: Tuesday, August 21, 2001 2:25 PM
> To: gentoo-dev@cvs.gentoo.org
> Subject: Re: [gentoo-dev] An Offering: the EMerge Interface
> 
> 
> Hi.
> 
> I've already added this to Gentool, but I've not checked it 
> into CVS yet (shame on me!).
> 
> If you have knowledge of Python (we don't use Perl for 
> Portage) and want to keep working on these kinds of things, 
> tell me, and I'll see if we can't get Gentool rolling a bit 
> faster from now on.
> 
> For those of you who haven't been paying attention to what I 
> intend to do with Gentool: It's intended as a playground for 
> higher-level stuff that should go into Portage. 
> 
> Since Portage itself is so vital, we don't want to muck 
> around with it needlessly. That's why I suggest we use 
> Gentool as an entry-point 
> for all crazy and non-crazy 'portage addons' that crop up on the list.
> 
> This way, the users will be able to try them out before they 
> make it into Portage proper, and we can throw away/rework 
> suggestions that weren't so hot after all.
> 
> 
> I promise to speed up Gentool development once I get settled 
> at uni (in 
> about a week).
> 
> 
> Kind regards,
> 
> Karl T
> 
> On Sun, Aug 19, 2001 at 10:10:53PM -0400, Will Rogers wrote:
> > # emi - the EMerge Interface
> > # Copyright (C) 2001 William J. Rogers (wjr@wam.umd.edu)
> > #
> > # An interface to the Gentoo Portage package system in the style of 
> > apt-get
> > 
> > Available at http://www.wam.umd.edu/~wjr/emi (also linked off of 
> > http://www.wam.umd.edu/~wjr).
> > 
> > This is a perl script that can acts as a user-friendly interface to 
> > emerge merge, package information, and ebuild unmerge 
> operations.  Its 
> > features include:
> > 	- emi merge <package file>
> > checks if there is an ebuild in the tree for this package 
> (if you are 
> > calling it on a binary .tbz2), lists currently installed versions, 
> > lists dependencies via emerge --pretend, and tells you if 
> those have 
> > ebuilds available also, then asks if you want to install 
> and fires off 
> > emerge if you say yes
> > 	- emi query <package name>
> > Lists ebuilds for this program in the portage tree, source 
> packages in 
> > the distfiles folder, binary packages in PKGDIR, and 
> current versions 
> > in /var/db/pkg
> > 	- emi unmerge <package name>
> > Lists current versions in /var/db/pkg and allows you to 
> select one to 
> > unmerge (via ebuild unmerge) or quit
> > 
> > I wrote this in my spare time over the weekend because I found it 
> > tiresome to manually look around to discover various 
> information about 
> > packages.  This functionality might be planned in future emerge 
> > iterations; it might already exist somewhere I haven't 
> found yet.  If 
> > so, I don't really care; I had fun writing it :).
> > 
> > Please check it out if you're interested and let me know what you 
> > think.
> > 
> > Will Rogers
> > wjr@wam.umd.edu
> > 
> > 
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@cvs.gentoo.org 
> > http://cvs.gentoo.org/mailman/listinfo/gentoo-dev
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@cvs.gentoo.org 
> http://cvs.gentoo.org/mailman/listinfo/gentoo-> dev
> 




  parent reply	other threads:[~2001-08-22  5:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-19 20:11 [gentoo-dev] An Offering: the EMerge Interface Will Rogers
2001-08-19 21:26 ` Ben Lutgens
2001-08-21 12:27 ` Karl Trygve Kalleberg
2001-08-21 14:27   ` Will Rogers
2001-08-22  0:00   ` Will Rogers [this message]
2001-08-22 16:23     ` Karl Trygve Kalleberg
  -- strict thread matches above, loose matches on Subject: below --
2001-08-22  0:01 Will Rogers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000301c12acf$9a904eb0$0801a8c0@saucer' \
    --to=wjr@wam.umd.edu \
    --cc=gentoo-dev@cvs.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox