[gentoo-portage-dev] Questions regarding the new portage API (savior branch)

2006-02-28 Thread Michael Schilling
Hello everyone,

some days ago I asked about a portage API on #gentoo-portage and they
pointed me to the new portage rewrite (saviour branch). Because I want
to do a complete OO rewrite of my program glcu (glcu.sf.net) a OO
portage API would be really useful. And I think this would be useful for
any other portage tool (e.g. porthole or everything in gentoo-
portage-tools ) as well. So before I write some extra stuff that can
only be applied to my program, it would probably be a lot better to
directly help with a high level portage API.  Therefore I would
appreciate it if someone could point me in the right direction. To be
able to start, I have a few questions:

- Is one of these svn-web-repository up to date?
  * http://sources.gentoo.org/viewcvs.py/portage/main/branches/savior/
  * http://mzz.mine.nu/bzr/savior-svn/portage/

- Where can I find general ideas about the functionality of the planned
  new portage API. (TODO files, anything about the general structure)

- Is any API functionality already implemented (so that I can learn how
  it is meant to work). Where can I find the corresponding files?

- When is the best time to find some people of the savior branch in
  #gentoo-portage (I don't have time to lure in the # all the time, but
  it's probably the best and quickest way to get more informations)


Any help is very much appreciated!


Bye,
Michael


-- 
Michael Schilling  

eMail : [EMAIL PROTECTED]
 URL  : http://glcu.sf.net/


Change my name I remain the same. - Moloko
-- 
gentoo-portage-dev@gentoo.org mailing list



[gentoo-portage-dev] vdb-update script (for global updates) with job progress framework

2006-02-28 Thread Zac Medico
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi everyone,

I've been working on a script for doing global updates on packages installed in 
the vdb (related to bug 122089).  It's called vdb-update [1] and it does 
basically the same thing as fixpackages but it works on installed packages 
instead of binary packages.  

vdb-update has the beginnings of a job progress framework that portage can use 
to run various time consuming tasks, display progress, and interrupt tasks when 
necessary.  When vdb-update and fixpackages are ready, I'd like to make both of 
them into emaint modules.

In order to run the script, you will need at least revision 2801 of portage, so 
I have made an svn snapshot and ebuild available [2] for the convenience of 
anyone who would like to try it.  Your feedback on vdb-update (in it's 
unfinished state) would be appreciated.

Zac

[1] http://dev.gentoo.org/~zmedico/portage/branches/2.1/bin/vdb-update.py
[2] 
http://dev.gentoo.org/~zmedico/overlay/sys-apps/portage/portage-2.1_pre20060228.ebuild
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD8DBQFEBE/l/ejvha5XGaMRAnOcAKCxYdG8h7akeAsszCzAiLwvNDV9pACcDjHL
wL1MNSdgd8ErKBn2JZlbwC0=
=wBRb
-END PGP SIGNATURE-
-- 
gentoo-portage-dev@gentoo.org mailing list



Re: [gentoo-portage-dev] vdb-update script (for global updates) with job progress framework

2006-02-28 Thread Jason Stubbs
On Tuesday 28 February 2006 22:28, Zac Medico wrote:
 vdb-update has the beginnings of a job progress framework that portage can 
 use to run various time consuming tasks, display progress, and interrupt 
 tasks when necessary.  When vdb-update and fixpackages are ready, I'd like 
 to make both of them into emaint modules.   

It's looking nice and clean at the moment. You might want to think twice about 
integrating it into emaint, though. Integrating the couple of things that 
emaint does into what you're working on would be much better. :)

Seriously, emaint was created in about 30 minutes to counter the regression 
of emerge warning on unsatisfiable world file entries. It was/is not meant to 
stand the test of time in its current state. Why would you want to muddy up 
your code with it? ;)

--
Jason Stubbs
-- 
gentoo-portage-dev@gentoo.org mailing list



Re: [gentoo-portage-dev] vdb-update script (for global updates) with job progress framework

2006-02-28 Thread Rumen Yotov
On Tuesday 28 February 2006 15:28, Zac Medico wrote:
 Hi everyone,

 I've been working on a script for doing global updates on packages
 installed in the vdb (related to bug 122089).  It's called vdb-update [1]
 and it does basically the same thing as fixpackages but it works on
 installed packages instead of binary packages.

 vdb-update has the beginnings of a job progress framework that portage can
 use to run various time consuming tasks, display progress, and interrupt
 tasks when necessary.  When vdb-update and fixpackages are ready, I'd like
 to make both of them into emaint modules.

 In order to run the script, you will need at least revision 2801 of
 portage, so I have made an svn snapshot and ebuild available [2] for the
 convenience of anyone who would like to try it.  Your feedback on
 vdb-update (in it's unfinished state) would be appreciated.

 Zac

 [1] http://dev.gentoo.org/~zmedico/portage/branches/2.1/bin/vdb-update.py
 [2]
 http://dev.gentoo.org/~zmedico/overlay/sys-apps/portage/portage-2.1_pre2006
0228.ebuild
Hi,
Thanks, it works for me.
Rumen


pgpn0ELB0VT2O.pgp
Description: PGP signature


Re: [gentoo-portage-dev] Switching LOCALE during build?

2006-02-28 Thread Mike Frysinger
On Tuesday 28 February 2006 10:55, Patrick Lauer wrote:
 During build portage should change the locale to en_us

no, C would be a saner setting

 so that any error 
 messages are easy to read even if the user has set it differently. This
 shouldn't affect users much and could get rid of the bugreports where it
 is hard to understand what went wrong because everything is in french.

i'm not sure how this would affect the build process ... it would for sure 
mask mistakes in ebuild/packages that assume certain things about the active 
local when using character classes in regular expressions
-mike
-- 
gentoo-portage-dev@gentoo.org mailing list



Re: [gentoo-portage-dev] Switching LOCALE during build?

2006-02-28 Thread Marius Mauch

Patrick Lauer wrote:

Hi all,

this is an idea we had at FOSDEM to make bugreports easier to read:

During build portage should change the locale to en_us so that any error
messages are easy to read even if the user has set it differently. This
shouldn't affect users much and could get rid of the bugreports where it
is hard to understand what went wrong because everything is in french.

Portage changes should be limited to setting LC_ALL in all subshells it
spawns.

Does this cause any unexpected problems? (Programs changing their
language during build would be one possible side-effect). Is it
needed/useful?

Thanks for any feedback,


http://bugs.gentoo.org/show_bug.cgi?id=57973
--
gentoo-portage-dev@gentoo.org mailing list