Mailinglist Archive: zypp-devel (115 mails)
| < Previous | Next > |
Re: [zypp-devel] pkg-bindings status
- From: Duncan Mac-Vicar Prett <dmacvicar@xxxxxxx>
- Date: Tue, 10 Jul 2007 12:14:53 +0200
- Message-id: <200707101214.54233.dmacvicar@xxxxxxx>
On Tuesday 10 July 2007 11:16:36 Lukas Ocilka wrote:
> Hi,
>
> I was asked to search through the installation for information which
> Pkg:: callbacks from the list are used and where. Here is the list what
> I've found, however it doesn't need to be the full list:
The question is, what are those functions supposed to do.
ZYpp semantics where something like:
restore sources to a global object
modify and operate over them
save them
In the new repo manager, zypp does not give you any object to operate onto.
You ask for known repos. Then you can tell RepoManager to delete a known
repo, but that has no relation with the repositories you have created in
memory.
Implementing them as the old way will make ZYpp act like it was before. That
means everything done in this 6 months is completely useless.
Duncan
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> Hi,
>
> I was asked to search through the installation for information which
> Pkg:: callbacks from the list are used and where. Here is the list what
> I've found, however it doesn't need to be the full list:
The question is, what are those functions supposed to do.
ZYpp semantics where something like:
restore sources to a global object
modify and operate over them
save them
In the new repo manager, zypp does not give you any object to operate onto.
You ask for known repos. Then you can tell RepoManager to delete a known
repo, but that has no relation with the repositories you have created in
memory.
Implementing them as the old way will make ZYpp act like it was before. That
means everything done in this 6 months is completely useless.
Duncan
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |