From: Brian <dol-sen@telus.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Hello! && portage UI
Date: Tue, 14 Mar 2006 06:39:35 -0800 [thread overview]
Message-ID: <1142347176.10776.26.camel@localhost> (raw)
In-Reply-To: <cea53e3c0603140314p4056fa6as@mail.gmail.com>
On Tue, 2006-14-03 at 13:14 +0200, tvali wrote:
> Ok, i was, yes, speaking about kde.
>
> I will check out this Porthole :) I was actually thinking more about c
> ++, but nothing against python -- i was quite a fan of python when i
> first found it.
I believe Kuroo is in C, maybe c++
>
> I'm new to gentoo, so could you tell me, where i find some clear
> manual for doing the following:
> * Download gentoo source of Porthole
First I would unmask it and emerge it so that you have all dependencies
installed. enable the debug use flag or emerge pycrash-0.43 separately.
# echo =app-portage/porthole-0.5.0 /etc/portage/package.unmask
# echo app-portage/porthole /etc/portage/package.keywords
# emerge porthole
If you like it and want to make a kde interface for it,
Go to our sourceforge page and do a cvs checkout.
http://sourceforge.net/projects/porthole/
> * Change that source
cd into the directory, edit as desired
> * Build my version of it in such way that my portage tree is OK after
> that
>
then run it from a terminal:
# ./porthole -l -d
Also sign up to the 2 mail lists for porthole so we can discuss any
problems, etc.. This list is for portage development.
Then any changes can be diffed for commit.
cvs diff -u > somefile
Of course I will have to make changes to the interface loading so that
your changes won't kill the gtk interface code.
> Are --fetchonly and --usepkgonly somehow related to that?
>
--fetchonly will just get the tarball downloaded into the distfiles
directory.
--usepkgonly is for telling emerge to use binary packages only.
> 2006/3/14, Brian <dol-sen@telus.net>:
> On Tue, 2006-14-03 at 00:39 +0200, tvali wrote:
> For KDE there are 2 projects that come to mind Kuroo, and
> another one
> that was designed to run in Konguerer, but I don't remember
> the name.
> Kuroo is being actively developed right now, I don't recall
> seeing
> anything recently on the other one.
>
> If your thinking of something being coded in python so that it
> can
> interact with and use portage code for information retrieval
> then check
> out Porthole. It is a gtk app not KDE, but will run on a KDE
> desktop.
> It sounds like it already does things similar to what you had
> in mind.
>
> If you wanted to port the gui code from pygtk to pyQt, I am
> sure that
> there would be a number of KDE users that would be pleased. I
> would
> definitely consider adding an optional KDE interface to it. :)
>
>
> --
> Brian <dol-sen@telus.net>
>
> --
> gentoo-portage-dev@gentoo.org mailing list
>
>
>
>
> --
> tvali
> (e-mail: "qtvali@gmail.com"; msn: "qtvali@gmail.com";
> icq: "317-492-912")
>
> Ühe eesti internetifirma lehel kohtasin tsitaati:
> If you don't do it excellently, dont do it at all. Because if it's not
> excellent, it won't be profitable or fun, and if you're not in
> business for fun or profit, what the hell are you doing here?
> Robert Townsend
--
Brian <dol-sen@telus.net>
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-14 14:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 22:39 [gentoo-portage-dev] Hello! && portage UI tvali
2006-03-14 0:54 ` Brian
2006-03-14 11:14 ` tvali
2006-03-14 14:39 ` Brian [this message]
2006-03-14 14:55 ` tvali
2006-03-14 15:07 ` Brian
2006-03-14 15:18 ` Marius Mauch
2006-03-14 16:48 ` tvali
2006-03-14 16:55 ` tvali
2006-03-15 9:51 ` Paul de Vrieze
2006-03-15 14:52 ` solar
2006-03-15 15:12 ` tvali
2006-03-15 16:36 ` solar
2006-03-15 17:36 ` tvali
2006-03-15 20:42 ` portage from C (was Re: [gentoo-portage-dev] Hello! && portage UI) Kevin F. Quinn (Gentoo)
2006-03-15 21:37 ` solar
2006-03-15 22:12 ` tvali
2006-03-15 22:14 ` tvali
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=1142347176.10776.26.camel@localhost \
--to=dol-sen@telus.net \
--cc=gentoo-portage-dev@lists.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