1 |
Dear Brian |
2 |
Thank you for your email. Good to know that somebody is actively |
3 |
working on this! |
4 |
Actually what I need is the ability for the user (not root) to create |
5 |
binary packages somewhere he can write (PKGDIR=somedir emerge -B |
6 |
somepkg). It would also be useful to also retrieve the installable |
7 |
packages matching a given pattern (e.g. eigen or dev-cpp/eigen or |
8 |
>=dev-cpp/eigen-3.0.0). |
9 |
|
10 |
I'm starting my project using the command-line interface to emerge and |
11 |
equery. When I feel your public_api are ready anough for my usege, I |
12 |
will switch to it, which won't be a big deal (I hope). |
13 |
|
14 |
-- |
15 |
Cheers |
16 |
Andrea Arteaga |
17 |
|
18 |
|
19 |
2011/5/23 Brian Dolbec <brian.dolbec@×××××.com>: |
20 |
> Andrea, use the public_api branch of the portage git repo as much as |
21 |
> possible. If there is additional functionality you need, then ask. I |
22 |
> will gladly try to get it for you if possible. I am just now adding |
23 |
> emerge capability to the api, so you should be able to use it later in |
24 |
> the project for emerging. I would however set up your code to be able |
25 |
> to run emerge from a subprocess. You should find the most common |
26 |
> information gathering functions in the api now. They should be fairly |
27 |
> straightforward to use. Keep in mind that the api is likely to change |
28 |
> somewhat yet as it is used more and improved. |
29 |
> |
30 |
> start by creating a portage.api.settings.PortageSettings instance |
31 |
> |
32 |
> Hopefully it will be merged into regular portage releases by the end of |
33 |
> this years gsoc. |
34 |
> |
35 |
> As for custom CFLAGS and other |
36 |
> variables, /etc/portage/env/$CAT/$pkg/files are used for individual pkg |
37 |
> overrides. As I've never used them I can't give you more detail about |
38 |
> it or where to look. |
39 |
> |
40 |
> If you need to write to those files, I would like to establish some code |
41 |
> in the api to standardize it and make it available for use. In the |
42 |
> meantime you can look if the one I use in porthole is suitable. I run |
43 |
> it as root from a terminal call or import it and use it directly the |
44 |
> importing code has the right privileges. |
45 |
> |
46 |
> http://porthole.git.sourceforge.net/git/gitweb.cgi?p=porthole/porthole;a=blob;f=porthole/backends/set_config.py;h=8e78126377f8fc79fc51f9d17499df48a2e0270e;hb=HEAD |
47 |
> |
48 |
> And if you need to keep an internal db of all those: |
49 |
> |
50 |
> http://porthole.git.sourceforge.net/git/gitweb.cgi?p=porthole/porthole;a=blob;f=porthole/db/user_configs.py;h=7f1c61459f26c6856f80d02cbdfb81ac3c04d7e2;hb=HEAD |
51 |
> |
52 |
> -- |
53 |
> Brian Dolbec <brian.dolbec@×××××.com> |
54 |
> |