[Cooker] New printing system

[Tiago Salem Herrmann]

Major Paine escreveu:

> Friday 08 August 2008 23:26:00 kirjutas Tiago Salem Herrmann:
>  
>> Major Paine wrote:
>>    
>>> Friday 08 August 2008 21:10:34 kirjutas Youp3:
>>>      
>>>> 2008/8/8 Tiago Salem Herrmann <salem@...>:
>>>>        
>>>>> Hi all,
>>>>>
>>>>> one of our plans for 2009.0 was to find a replacement for printerdrake.
>>>>> The most obvious choice was to use system-config-printer, as it is
>>>>> still under development and is the default tool in other distributions
>>>>> as well. Unfortunately it is not easy to replace a tool that is present
>>>>> in the distro for a long time, because it has a good integration and a
>>>>> lot of workarounds for many kinds of printers.
>>>>> I've been working basically in two packages to try to provide a new
>>>>> printing system,
>>>>> they are:
>>>>>
>>>>> 1) system-config-printer: provides the interface to add, remove, share
>>>>> printers. Provides
>>>>> a system tray applet which notifies the user about printing events and
>>>>> eventually asks the user to install required packages or missing
>>>>> firmware.
>>>>>
>>>>> 2) hal-cups-utils: in charge of detecting new printers, notify the
>>>>> applet to let the
>>>>> user know about what is going on, choose the better printer model, and
>>>>> so on.
>>>>>
>>>>> Me and Vanessa have tested some printers and it seems that it is
>>>>> working as expected,
>>>>> but as we can't have all the supported printers to test if everything
>>>>> is ok, it would be great if we could have some help from everybody.
>>>>>
>>>>> "urpmi system-config-printer" should be enough to disable the old
>>>>> printer detection system
>>>>> and enable the new one. (don't forget to restart the session)
>>>>> Usb printers are detected when you plug them in the system. To add
>>>>> parallel printers
>>>>> you must open system-config-printer and do the work manually.
>>>>>
>>>>> Some strings are not translated, both because they are not translated
>>>>> in upstream and
>>>>> because some strings were introduced only in mandriva version. I plan
>>>>> to put the po files
>>>>> in the svn soft (just like it is done in printerdrake), so then the
>>>>> contributors can
>>>>> help on translation.
>>>>>
>>>>> For a while, printerdrake and system-config-printer can coexist.
>>>>> If we decide that the new printing system is ok, we can drop
>>>>> printerdrake (or provide it in contrib?),
>>>>> and if we decide it is too early to replace printerdrake by
>>>>> system-config-printer, we can drop
>>>>> system-config-printer and go back to the place where we were before.
>>>>>
>>>>>
>>>>> Thank you.
>>>>>
>>>>> --
>>>>> Tiago Salem Herrmann
>>>>>          
>>>> Hello
>>>>
>>>> It seem to work fined with my HP Photosmart 3210.
>>>>
>>>> But I see a major regression with this tool compared to printerdrake.
>>>> There is no auto detection system for network printer. I need to enter
>>>> manually printer IP address. Printerdrake can auto detect my printer.
>>>> So yet printerdrake is more user-friendly for network printers.
>>>>        
>>> Strange, it finds all my network printers (samsung's kyoceras hp) and it
>>> does it a lot quicker then printerdrake but when it lets to chose driver
>>> there are so few options, like no samsung and kyocera :)
>>>      
>> hmm, do you have task-printing-misc installed?
>> what happens if you install it, and then try to reconfigure your printer?
>>    
>
> In my case it wasn't I urpmi'ed it and now I can see all of them. It seems
> that the system-config-printer doesn't require task-printing-misc
>  

Yes, it does not require it because it should be installed on demand. I
believe it is working for local printers only. I'll try to find a
network printer here to fix this.
Thanks.

[Tiago Salem Herrmann]

Marcelo Ricardo Leitner escreveu:

> Tiago Salem Herrmann escreveu:
>>
>>
>> For a while, printerdrake and system-config-printer can coexist.
>> If we decide that the new printing system is ok, we can drop
>> printerdrake (or provide it in contrib?),
>> and if we decide it is too early to replace printerdrake by
>> system-config-printer, we can drop
>> system-config-printer and go back to the place where we were before.
>
> That's a really big move, congrats to all involved, specially Salem :)

thanks :)
>
> I know Salem and Vanessa probably handled theses tests on their shots,
> but IMHO it's nice to make them public so people can try them out too.
>
> There are some combinations that should work too, like:
> * Boot with the unconfigured printer already plugged in (cold plug),
> you should be able to setup the printer after the first graphical login.
Yes, Vanessa warned me about it. It can be useful, but IMO, could be
annoying in some cases as well. For example, if an user has a printer
that can't be
installed on linux (multifunctional?) and uses another operating system
in the same computer that supports this printer, every time the user
boots on mandriva it will warn the user about a printer that can't be
installed. But if the user really wants to install this printer, it is
possible to access system-config-printer through menu, or mcc, when I
finish the integration.
>
> * Remove a configured printer while on system, reboot without it,
> reboot again and plug it back (it shouldn't trigger 'a new printer..'
> wizard)
What you mean remove? remove the queue from cups, or remove the device
from the computer?
If you mean remove from the computer, it is working. hal_lpadmin checks
if there is the same id in cups and only re-enable the queue.
(and notify the user that it was re-enabled).
The way it works now: there is no wizard, when you plug your printer and
you have all the needed software installed, it will
automatically install your printer and only notify the user about what
was done in a popup. At least I can't see any reasons someone would
connect a printer to the computer and refuse the installation. If it is
plugged, it is because the user wants it to be installed.
>
> That's what I recall for now, I'll come back if I have new ideas :)
>
> I'll do some tests with my hp 1018 as soon as I finish upgrading my
> box over here.
It requires firmware upload, right?
Wait for your feedback :)

[Marcelo Ricardo Leitner-3]

Tiago Salem Herrmann escreveu:

> Marcelo Ricardo Leitner escreveu:
>> Tiago Salem Herrmann escreveu:
>>>
>>>
>>> For a while, printerdrake and system-config-printer can coexist.
>>> If we decide that the new printing system is ok, we can drop
>>> printerdrake (or provide it in contrib?),
>>> and if we decide it is too early to replace printerdrake by
>>> system-config-printer, we can drop
>>> system-config-printer and go back to the place where we were before.
>>
>> That's a really big move, congrats to all involved, specially Salem :)
> thanks :)
>>
>> I know Salem and Vanessa probably handled theses tests on their shots,
>> but IMHO it's nice to make them public so people can try them out too.
>>
>> There are some combinations that should work too, like:
>> * Boot with the unconfigured printer already plugged in (cold plug),
>> you should be able to setup the printer after the first graphical login.
> Yes, Vanessa warned me about it. It can be useful, but IMO, could be
> annoying in some cases as well. For example, if an user has a printer
> that can't be
> installed on linux (multifunctional?) and uses another operating system
> in the same computer that supports this printer, every time the user
> boots on mandriva it will warn the user about a printer that can't be
> installed. But if the user really wants to install this printer, it is
> possible to access system-config-printer through menu, or mcc, when I
> finish the integration.

Hmm.. I don't know if that would be the case, as (at least printerdrake
had it) should be possible to to mark something like 'do not try to
setup this printer anymore'

Anyway, despite of the feature, IMHO it's a very rare scenario a user
that uses linux and has an unsupported printer. Now remember the common
procedure inherited from Windows: plug in and restart the system. That's
user friendly as it is on their blood already heh.

>> * Remove a configured printer while on system, reboot without it,
>> reboot again and plug it back (it shouldn't trigger 'a new printer..'
>> wizard)
> What you mean remove? remove the queue from cups, or remove the device
> from the computer?
> If you mean remove from the computer, it is working. hal_lpadmin checks

Ops, sorry, that's what I meant, unplug it.

> if there is the same id in cups and only re-enable the queue.
> (and notify the user that it was re-enabled).

Cool :)

> The way it works now: there is no wizard, when you plug your printer and
> you have all the needed software installed, it will
> automatically install your printer and only notify the user about what
> was done in a popup. At least I can't see any reasons someone would
> connect a printer to the computer and refuse the installation. If it is
> plugged, it is because the user wants it to be installed.

For sure, +1!

>> That's what I recall for now, I'll come back if I have new ideas :)
>>
>> I'll do some tests with my hp 1018 as soon as I finish upgrading my
>> box over here.
> It requires firmware upload, right?
> Wait for your feedback :)

Yes, that's the tricky one. I'm downloading tons of updates, maybe
tomorrow or next week at most I can do some testing.

Btw, new test: damn, just forgot.
(4mins after) Oh, remembered: I couldn't check how system-config-printer
is integrated with urpmi, but I assume it is via subprocessing/fork.
That would be less problematic, but it would be nice to test installing
required packages from the 3 CDs set, which I'm almost sure it will
request a media change. Just to be sure that this working properly :)

Cya
Marcelo

[Tiago Salem Herrmann]

Marcelo Ricardo Leitner escreveu:

> Tiago Salem Herrmann escreveu:
>> Yes, Vanessa warned me about it. It can be useful, but IMO, could be
>> annoying in some cases as well. For example, if an user has a printer
>> that can't be
>> installed on linux (multifunctional?) and uses another operating
>> system in the same computer that supports this printer, every time
>> the user boots on mandriva it will warn the user about a printer that
>> can't be installed. But if the user really wants to install this
>> printer, it is possible to access system-config-printer through menu,
>> or mcc, when I finish the integration.
>
> Hmm.. I don't know if that would be the case, as (at least
> printerdrake had it) should be possible to to mark something like 'do
> not try to setup this printer anymore'

Hmm, I'll take a look at the code and check what I can do.
I'm trying not to change the code too much, or it will be necessary to
fork system-config-printer, and that is not the idea.
>
> Anyway, despite of the feature, IMHO it's a very rare scenario a user
> that uses linux and has an unsupported printer. Now remember the
> common procedure inherited from Windows: plug in and restart the
> system. That's user friendly as it is on their blood already heh.
yes, I'm trying not to use windows as a reference of usability :)
>
> Btw, new test: damn, just forgot.
> (4mins after) Oh, remembered: I couldn't check how
> system-config-printer is integrated with urpmi, but I assume it is via
> subprocessing/fork. That would be less problematic, but it would be
> nice to test installing required packages from the 3 CDs set, which
> I'm almost sure it will request a media change. Just to be sure that
> this working properly :)

Yes, it calls gurpmi, and I believe it will mange these package stuffs.
but I'll test it for sure.

[Olivier Blin-2]

Tiago Salem Herrmann <salem@...> writes:

>> Btw, new test: damn, just forgot.
>> (4mins after) Oh, remembered: I couldn't check how
>> system-config-printer is integrated with urpmi, but I assume it is
>> via subprocessing/fork. That would be less problematic, but it would
>> be nice to test installing required packages from the 3 CDs set,
>> which I'm almost sure it will request a media change. Just to be
>> sure that this working properly :)
>
> Yes, it calls gurpmi, and I believe it will mange these package
> stuffs. but I'll test it for sure.

Couldn't it use packagekit instead?
It would avoid maintaining a gurpmi backend

--
Olivier Blin (blino) - Mandriva

[Steve Morris-5]

Tiago Salem Herrmann wrote:

> Major Paine escreveu:
>> Friday 08 August 2008 23:26:00 kirjutas Tiago Salem Herrmann:
>>  
>>> Major Paine wrote:
>>>    
>>>> Friday 08 August 2008 21:10:34 kirjutas Youp3:
>>>>      
>>>>> 2008/8/8 Tiago Salem Herrmann <salem@...>:
>>>>>        
>>>>>> Hi all,
>>>>>>
>>>>>> one of our plans for 2009.0 was to find a replacement for
>>>>>> printerdrake.
>>>>>> The most obvious choice was to use system-config-printer, as it is
>>>>>> still under development and is the default tool in other
>>>>>> distributions
>>>>>> as well. Unfortunately it is not easy to replace a tool that is
>>>>>> present
>>>>>> in the distro for a long time, because it has a good integration
>>>>>> and a
>>>>>> lot of workarounds for many kinds of printers.
>>>>>> I've been working basically in two packages to try to provide a new
>>>>>> printing system,
>>>>>> they are:
>>>>>>
>>>>>> 1) system-config-printer: provides the interface to add, remove,
>>>>>> share
>>>>>> printers. Provides
>>>>>> a system tray applet which notifies the user about printing
>>>>>> events and
>>>>>> eventually asks the user to install required packages or missing
>>>>>> firmware.
>>>>>>
>>>>>> 2) hal-cups-utils: in charge of detecting new printers, notify the
>>>>>> applet to let the
>>>>>> user know about what is going on, choose the better printer
>>>>>> model, and
>>>>>> so on.
>>>>>>
>>>>>> Me and Vanessa have tested some printers and it seems that it is
>>>>>> working as expected,
>>>>>> but as we can't have all the supported printers to test if
>>>>>> everything
>>>>>> is ok, it would be great if we could have some help from everybody.
>>>>>>
>>>>>> "urpmi system-config-printer" should be enough to disable the old
>>>>>> printer detection system
>>>>>> and enable the new one. (don't forget to restart the session)
>>>>>> Usb printers are detected when you plug them in the system. To add
>>>>>> parallel printers
>>>>>> you must open system-config-printer and do the work manually.
>>>>>>
>>>>>> Some strings are not translated, both because they are not
>>>>>> translated
>>>>>> in upstream and
>>>>>> because some strings were introduced only in mandriva version. I
>>>>>> plan
>>>>>> to put the po files
>>>>>> in the svn soft (just like it is done in printerdrake), so then the
>>>>>> contributors can
>>>>>> help on translation.
>>>>>>
>>>>>> For a while, printerdrake and system-config-printer can coexist.
>>>>>> If we decide that the new printing system is ok, we can drop
>>>>>> printerdrake (or provide it in contrib?),
>>>>>> and if we decide it is too early to replace printerdrake by
>>>>>> system-config-printer, we can drop
>>>>>> system-config-printer and go back to the place where we were before.
>>>>>>
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>> --
>>>>>> Tiago Salem Herrmann
>>>>>>          
>>>>> Hello
>>>>>
>>>>> It seem to work fined with my HP Photosmart 3210.
>>>>>
>>>>> But I see a major regression with this tool compared to printerdrake.
>>>>> There is no auto detection system for network printer. I need to
>>>>> enter
>>>>> manually printer IP address. Printerdrake can auto detect my printer.
>>>>> So yet printerdrake is more user-friendly for network printers.
>>>>>        
>>>> Strange, it finds all my network printers (samsung's kyoceras hp)
>>>> and it
>>>> does it a lot quicker then printerdrake but when it lets to chose
>>>> driver
>>>> there are so few options, like no samsung and kyocera :)
>>>>      
>>> hmm, do you have task-printing-misc installed?
>>> what happens if you install it, and then try to reconfigure your
>>> printer?
>>>    
>>
>> In my case it wasn't I urpmi'ed it and now I can see all of them. It
>> seems that the system-config-printer doesn't require task-printing-misc
>>  
> Yes, it does not require it because it should be installed on demand.
> I believe it is working for local printers only. I'll try to find a
> network printer here to fix this.
> Thanks.
>

I have installed system-config-printer and am wondering why we have it.

It seems to me to offer nothing over printerdrake (which I must add I
hardly ever use), and it certainly is not a patch on the configuration
capabilities offered by cups (but then neither is printerdrake).
Also I cannot find any menu entries or hook into drakconf. I you are
even thinking about making this useful then you need to provide either
of these or ideally both.
Just my 2 cents worth.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Tiago Salem Herrmann]

Steve Morris escreveu:

> Tiago Salem Herrmann wrote:  
>> Yes, it does not require it because it should be installed on demand.
>> I believe it is working for local printers only. I'll try to find a
>> network printer here to fix this.
>> Thanks.
>>
> I have installed system-config-printer and am wondering why we have
> it. It seems to me to offer nothing over printerdrake (which I must
> add I hardly ever use), and it certainly is not a patch on the
> configuration capabilities offered by cups (but then neither is
> printerdrake).

We have it because it is not very easy to maintain an internal tool, and
using a tool that is still under development and used by other distros
seems to be better, since everybody can contribute to improve it.
system-config-printer IMO has a more user friendly interface, and is
up-to-date with new technologies: dbus + hal (hal-cups-utils).
Besides that, there is nobody developing printerdrake at this moment.

> Also I cannot find any menu entries or hook into drakconf. I you are
> even thinking about making this useful then you need to provide either
> of these or ideally both.
Yes, as I said in a previous email, I'll integrate it in mcc.
the package provides the desktop files, and at least here I have this:
Menu->tools->system tools->printing

[Tiago Salem Herrmann]

Olivier Blin escreveu:

> Tiago Salem Herrmann <salem@...> writes:
>
>  
>>> Btw, new test: damn, just forgot.
>>> (4mins after) Oh, remembered: I couldn't check how
>>> system-config-printer is integrated with urpmi, but I assume it is
>>> via subprocessing/fork. That would be less problematic, but it would
>>> be nice to test installing required packages from the 3 CDs set,
>>> which I'm almost sure it will request a media change. Just to be
>>> sure that this working properly :)
>>>      
>> Yes, it calls gurpmi, and I believe it will mange these package
>> stuffs. but I'll test it for sure.
>>    
>
> Couldn't it use packagekit instead?
> It would avoid maintaining a gurpmi backend
>
>  

Yes, is packagekit planned to be moved to main?
I'll need to study how it works, but I think it is possible.

[Adam Williamson-4]

On Sat, 2008-08-09 at 14:32 -0300, Marcelo Ricardo Leitner wrote:

> Anyway, despite of the feature, IMHO it's a very rare scenario a user
> that uses linux and has an unsupported printer.

Erm - have you checked out the Printers and Scanners forum lately?

http://forum.mandriva.com/viewforum.php?f=13&sid=2cae63f5b51233345a77b428d4069071
--
adamw

[Steve Morris-5]

Tiago Salem Herrmann wrote:

> Steve Morris escreveu:
>> Tiago Salem Herrmann wrote:
>>> Yes, it does not require it because it should be installed on
>>> demand. I believe it is working for local printers only. I'll try to
>>> find a network printer here to fix this.
>>> Thanks.
>>>
>> I have installed system-config-printer and am wondering why we have
>> it. It seems to me to offer nothing over printerdrake (which I must
>> add I hardly ever use), and it certainly is not a patch on the
>> configuration capabilities offered by cups (but then neither is
>> printerdrake).
> We have it because it is not very easy to maintain an internal tool,
> and using a tool that is still under development and used by other
> distros seems to be better, since everybody can contribute to improve it.
> system-config-printer IMO has a more user friendly interface, and is
> up-to-date with new technologies: dbus + hal (hal-cups-utils).

The only advantage this interface may have over printerdrake is that it

looks like the windows print monitor.
> Besides that, there is nobody developing printerdrake at this moment.
>
>> Also I cannot find any menu entries or hook into drakconf. I you are
>> even thinking about making this useful then you need to provide
>> either of these or ideally both.
> Yes, as I said in a previous email, I'll integrate it in mcc.
> the package provides the desktop files, and at least here I have this:
> Menu->tools->system tools->printing
>
I have it now too. It doesn't appear in KDE4 until one reboots, a logout
and log back in again doesn't produce it.

regards,
Steve


[samorris.vcf]

---

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@...
x-mozilla-html:TRUE
version:2.1
end:vcard

---

[Frederic Crozat]

Le dimanche 10 août 2008 à 14:02 -0300, Tiago Salem Herrmann a écrit :

> Olivier Blin escreveu:
> > Tiago Salem Herrmann <salem@...> writes:
> >
> >  
> >>> Btw, new test: damn, just forgot.
> >>> (4mins after) Oh, remembered: I couldn't check how
> >>> system-config-printer is integrated with urpmi, but I assume it is
> >>> via subprocessing/fork. That would be less problematic, but it would
> >>> be nice to test installing required packages from the 3 CDs set,
> >>> which I'm almost sure it will request a media change. Just to be
> >>> sure that this working properly :)
> >>>      
> >> Yes, it calls gurpmi, and I believe it will mange these package
> >> stuffs. but I'll test it for sure.
> >>    
> >
> > Couldn't it use packagekit instead?
> > It would avoid maintaining a gurpmi backend
> >
> >  
> Yes, is packagekit planned to be moved to main?
> I'll need to study how it works, but I think it is possible.

I'm not opposed to the idea but we are still missing some notification
callbacks in urpmi backend of PackageKit (Aurelien is supposed to take
care of that this month). Moreover, we would need to ensure it doesn't
interact incorrectly with our Mandriva tools and doesn't try to
duplicate Mandriva tools (mdkapplet) by default.

--
Frederic Crozat <fcrozat@...>
Mandriva

[Fabrice FACORAT]

2008/8/11 Frederic Crozat <fcrozat@...>:

> Le dimanche 10 août 2008 à 14:02 -0300, Tiago Salem Herrmann a écrit :
>> Olivier Blin escreveu:
>> > Tiago Salem Herrmann <salem@...> writes:
>> >
>> >
>> >>> Btw, new test: damn, just forgot.
>> >>> (4mins after) Oh, remembered: I couldn't check how
>> >>> system-config-printer is integrated with urpmi, but I assume it is
>> >>> via subprocessing/fork. That would be less problematic, but it would
>> >>> be nice to test installing required packages from the 3 CDs set,
>> >>> which I'm almost sure it will request a media change. Just to be
>> >>> sure that this working properly :)
>> >>>
>> >> Yes, it calls gurpmi, and I believe it will mange these package
>> >> stuffs. but I'll test it for sure.
>> >>
>> >
>> > Couldn't it use packagekit instead?
>> > It would avoid maintaining a gurpmi backend
>> >
>> >
>> Yes, is packagekit planned to be moved to main?
>> I'll need to study how it works, but I think it is possible.
>
> I'm not opposed to the idea but we are still missing some notification
> callbacks in urpmi backend of PackageKit (Aurelien is supposed to take
> care of that this month). Moreover, we would need to ensure it doesn't
> interact incorrectly with our Mandriva tools and doesn't try to
> duplicate Mandriva tools (mdkapplet) by default.

ohhhj, so there's an urpmi backend for packagekit then ?
cvs link somewhere ? code ? screenshots ?



--
Close the World, Open the Net
http://www.linux-wizard.net

[Olivier Blin-2]

"Fabrice Facorat" <fabrice.facorat@...> writes:

> 2008/8/11 Frederic Crozat <fcrozat@...>:
>>
>> I'm not opposed to the idea but we are still missing some notification
>> callbacks in urpmi backend of PackageKit (Aurelien is supposed to take
>> care of that this month). Moreover, we would need to ensure it doesn't
>> interact incorrectly with our Mandriva tools and doesn't try to
>> duplicate Mandriva tools (mdkapplet) by default.
>
> ohhhj, so there's an urpmi backend for packagekit then ?
> cvs link somewhere ? code ? screenshots ?

The urpmi backend has been developped by Mandriva (more precisely by
Aurelien Lefebvre), and is now included upstream.
So it's also available in our packagekit package (in contrib)

--
Olivier Blin (blino) - Mandriva

[Fabrice FACORAT]

2008/8/12 Olivier Blin <blino@...>:

> "Fabrice Facorat" <fabrice.facorat@...> writes:
>
>> 2008/8/11 Frederic Crozat <fcrozat@...>:
>>>
>>> I'm not opposed to the idea but we are still missing some notification
>>> callbacks in urpmi backend of PackageKit (Aurelien is supposed to take
>>> care of that this month). Moreover, we would need to ensure it doesn't
>>> interact incorrectly with our Mandriva tools and doesn't try to
>>> duplicate Mandriva tools (mdkapplet) by default.
>>
>> ohhhj, so there's an urpmi backend for packagekit then ?
>> cvs link somewhere ? code ? screenshots ?
>
> The urpmi backend has been developped by Mandriva (more precisely by
> Aurelien Lefebvre), and is now included upstream.
> So it's also available in our packagekit package (in contrib)

didn't knew about this.
What features are supported ?
I will give it a try and blog about it.


--
Close the World, Open the Net
http://www.linux-wizard.net

[Frederic Crozat]

Le mardi 12 août 2008 à 14:30 +0200, Fabrice Facorat a écrit :

> 2008/8/12 Olivier Blin <blino@...>:
> > "Fabrice Facorat" <fabrice.facorat@...> writes:
> >
> >> 2008/8/11 Frederic Crozat <fcrozat@...>:
> >>>
> >>> I'm not opposed to the idea but we are still missing some notification
> >>> callbacks in urpmi backend of PackageKit (Aurelien is supposed to take
> >>> care of that this month). Moreover, we would need to ensure it doesn't
> >>> interact incorrectly with our Mandriva tools and doesn't try to
> >>> duplicate Mandriva tools (mdkapplet) by default.
> >>
> >> ohhhj, so there's an urpmi backend for packagekit then ?
> >> cvs link somewhere ? code ? screenshots ?
> >
> > The urpmi backend has been developped by Mandriva (more precisely by
> > Aurelien Lefebvre), and is now included upstream.
> > So it's also available in our packagekit package (in contrib)
>
> didn't knew about this.

Well, it was part of Mandriva Linux 2009.0 specs :)

> What features are supported ?

Check upstream website, they have a matrix of feature supported by each
backend.

--
Frederic Crozat <fcrozat@...>
Mandriva