I don't rely on aria2. What we need is the possibility to have some influence on the network transfer options like having client-cert based https auth (I need that for a PCI projekt in the moment). But other requests of this kind may be follow in the future. So if multicurl does fulfill this requirement I would like to see it for yast2-transfer as well. That would also simplify development process if the same libraries will be used for yast-transfer and package-transfer.
Uwe Gansert firstname.lastname@example.org schrieb am 7/27/2011 um 14.45 Uhr in Nachricht
on Wednesday 27 July 2011 Jochen Schaefer wrote:
However I got aria2c working within inst environment by using dud's for aria2 and libsqlite3 (needed by aria2). I'm wondering why yast is using aria2c for retriewing of packages from install source but not for autoyast relevant meta data like profile and rules.
because those are two completely independent and different parts. Developed by different people at different times in different projects. One is zypp, the other one is yast2-transfer. BTW, zypp is not using (supporting) aria2c anymore because it's simply broken und unreliable (aria2c I mean). multicurl is the new black and is used by zypp now but yast2-transfer is still on libcurl
So the questions are: If aria2c is available why is it not used for the whole autoyast remote network connections Would it be senseful to have an enhancement request for that or are there some drawbacks which I'm not aware of
I don't think that makes sense since we are on multicurl in the meantime. Maybe an evaluation of multicurl for yast2-transfer would make sense but I don't want to put aria2c support into it.