-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
René 'Necoro' Neumann wrote:
> Hi,
>
> I think, this is already somewhere on the agenda of portage (perhaps
> with a low priority
), but I nevertheless wanted to ask for the
> possibility to have as much of emerge's functionality exported in an API
> as possible =).
>
> The reason behind this is, that for Portato (this GUI thingy
), I have
> to re-implement lots of things that portage does (update functionality,
> parts of dep-string parsing etc). This is kind of sisyphean, because one
> has to:
> - notice/detect subtle changes (esp. the updating process often changes
> unnoticed in small points)
> - support tons of portage versions
>
> Especially with larger bumps (2.1.1 -> 2.1.2; -> 2.2) there are lots of
> things breaking and showing another behavior.
>
> In the sum, this work takes quite a large part of the whole development
> process ... though showing no results for the user
>
> Thus, it would be really great, if I only had to use an API (which might
> change over time - but API changes are easier to track and to work around).
> Perhaps - as you currently seem to be restructuring the whole thing -
> you can bundle some things and export them
. I bet there are more
> people out there besides me, that use or want to use the portage API and
> would be thankful, when they don't have to reinvent things
Thanks for expressing your interest. Lots of things are about ready
to be exposed for external use now, so I'll try to focus on
splitting them out for API consumers as soon as I can. Maybe we can
expose some of these things before the 2.2 final release.
Zac
>
> Else - thank you guys for your great work
. It's very great to see
> portage's evolution over the last months.
>
> Regards,
> René
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkiNePEACgkQ/ejvha5XGaNHqgCdGvfawDlGBT8e9Puh/usRSzL6
CMkAn35A/M2RGEnkUqUbxGMmqqsHQz1b
=XqiN
-----END PGP SIGNATURE-----
Exporting basic emerge/portage functionality in an API
