March 2009 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] zypper speed indication
by Dominique Leuenberger 16 Mar '09

16 Mar '09

Hi everybody, just a short question, I'm sure you already spotted it and it is fixed 'somewhere'.. (but not yet in oS:Factory). I'm performing a zypper dup and it tells me nicely it's downloading all the packages with an indication in B/s (so Bytes per second). I very much hope it is kidding: the number hardly goes beyond 150 B/s. If I verify gnome-system-monitor, I can see transfers of about 150 KB/s... so I assume that simply the K is missing in the output? Normally I'm very fast in canceling a transfer at that speed: I would never let it download 1GB like that ;) Dominique -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

5 6

[zypp-devel] [zypp trunk] Install srcpackage _without_ build deps.
by Michael Andres 12 Mar '09

12 Mar '09

With libzypp-6.3.0 build dependencies of srcpackages selected in the pool will not be resolved per default. There is a solver option to enable this (setSolveSrcPackages), but I'd recommend not to use it. Esp. if you install older version, the results are 'strange'. We will allow to define solving of build deps per source package (via ResStatus). With this the UIs should be able to provide a SrcPackage view. Note: Only srcpackages selected in the pool will be omitted. A solver request requiring a source package will be solved. For this we'd need support in the satsolver (sort of 'nodeps' flag). -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] Python Bindings and RepoInfo.baseUrls()
by Jan Blunck 12 Mar '09

12 Mar '09

I have the following example: import zypp def main(): myRepoInfo = zypp.RepoInfo() myRepoInfo.addBaseUrl(zypp.Url("file:///mounts/mirror/SuSE/ftp.opensuse.org/srv/ftp/pub/opensuse/debug/upda…")) myRepoInfo.setAlias("default") myRepoInfo.setName("default") myRepoInfo.setEnabled(True) myRepoInfo.setType(zypp.RepoType.RPMMD) # for now myRepoInfo.setGpgCheck(False) for url in myRepoInfo.baseUrls(): print url if __name__ == "__main__": main() When I let it run I get the following error: $ python baseurls.py swig/python detected a memory leak of type 'std::set< zypp::Url,std::less<zypp::Url >,std::allocator< zypp::Url > > *', no destructor found. Traceback (most recent call last): File "baseurls.py", line 16, in <module> main() File "baseurls.py", line 12, in main for url in myRepoInfo.baseUrls(): TypeError: 'PySwigObject' object is not iterable It somehow seems that the python bindings are incomplete. Any SWIG expert that can help me here? Cheers, Jan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 4

[zypp-devel] White on White is hard to read - or - How to get rid of zypper colors?
by Michael Andres 12 Mar '09

12 Mar '09

Hi! IMO color is a matter of taste and should not be activated by default. See noread.png. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+

2 1

[zypp-devel] New solver call : resolveQueue
by Stefan Schubert 11 Mar '09

11 Mar '09

Hi, apart from the solver call "resolvePool" ( collect all transactions from the pool, solving this transactions and writing the result back to pool) the solver can work off a given request queue too: /** * Resolve package dependencies: * * The solver works off the given queue and writes back the solution * to pool. * * Returns "true" on success (i.e., if there were no problems that * need user interaction) and "false" if there were problems. In * the latter case, use problems() and later applySolutions() * below. **/ bool resolveQueue (solver::detail::SolverQueueItemList & queue); The queue can have elements which are described in the following classes: base class: SolverQueueItem.h SolverQueueItemDelete.h SolverQueueItemInstall.h SolverQueueItemLock.h SolverQueueItemInstallOneOf.h SolverQueueItemUpdate.h Known problems: - The update and InstallOneOf request does not work correctly. - The error messages are too abstract now for the user. (Jano, you can start implementation now :-) ) Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

6 12

[zypp-devel] Re: Fixed noarch->anyarch and vice-versa update
by Michael Schroeder 11 Mar '09

11 Mar '09

On Tue, Mar 10, 2009 at 07:20:52PM +0100, JÃ¡n Kupec wrote: > Fixed noarch->anyarch and vice-versa update (bnc #483179). > > 'zypper up foo' would not find a non-noarch update of foo if the > installed arch was noarch, and vice-versa (anyarch->noarch), while > zypper 'list-updates' doUpdate() shows the update. > [... lots of code ...] Sorry, but the check if an architecture can replace an installed architecture belongs in libzypp, not zypper. If libzypp is lacking functions, they have to be added. It makes no sense to clutter all applications using libzypp with some implementations that have to be kept up to date. Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 1

[zypp-devel] Augeas for libzypp and zypper?
by Jan Kupec 10 Mar '09

10 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (orignal text at http://jniq.blogspot.com/2009/03/augeas-for-libzypp-and-zypper.html reposting for discussion) - ------copy------ The need for a configuration file for zypper (plus my wish for a nice CLI for handling it) and a visit to Raphaël Pinson's presentation at FOSDEM made me look at Augeas closely. Augeas enables you to read and edit your config files in a way which preserves comments and formatting details, allowing humans and programs coexist peacefully when it comes to editing configuration files. More than that, you can map some special structures of the file to special parts of the augeas tree, rather than using the generic INI file parser. See the zypp.conf for example (zypper.conf will have the same structure): [main] ## Option description. ## Default: etc. ## # disabledoption = value ## Another option description ## another.option = value With Augeas you can write a lens (the file contents description) which will map such file into a tree like this: /files/etc/zypp/zypp.conf/main/1 /files/etc/zypp/zypp.conf/main/1/description[1] = "Option description." /files/etc/zypp/zypp.conf/main/1/description[2] = "Default: etc." /files/etc/zypp/zypp.conf/main/1/description[3] /files/etc/zypp/zypp.conf/main/1/commented /files/etc/zypp/zypp.conf/main/1/disabledoption = "value" /files/etc/zypp/zypp.conf/main/2 /files/etc/zypp/zypp.conf/main/2/description[1] = "Another option description." /files/etc/zypp/zypp.conf/main/2/description[2] /files/etc/zypp/zypp.conf/main/2/another.option = "value" Note the commented node. Augeas has an API for looking for the nodes, getting values from them, setting the values, and finally saving the tree back to the config file. What does this mean for zypper? Implementing zypper conf --list is a piece of cake, as well as zypper conf --set another.option value. Commenting or uncommenting the option is a matter of adding or removing the commented node. Getting the option description for zypper conf - --help some.option is easy (and maybe it is possible to map the multi-line ## description to a single 'description' node!). Here is a draft of lens for zypper (it will need comments and further improvements). To try it out you can crete a /etc/zypp/zypper.conf file with contents like the above example, and use the augtool like this: $ augtool -I /the/dir/with/the/zypper.aug/file augtool> print /files/etc/zypp/zypper.conf/ /files/etc/zypp/zypper.conf /files/etc/zypp/zypper.conf/anon /files/etc/zypp/zypper.conf/anon/description[1] = "Configuration file for zypper" /files/etc/zypp/zypper.conf/anon/description[2] /files/etc/zypp/zypper.conf/anon/description[3] = "Boolean values are 0 1 yes no on off true false" /files/etc/zypp/zypper.conf/main /files/etc/zypp/zypper.conf/main/1 /files/etc/zypp/zypper.conf/main/1/description[1] = "Whether to use colors" /files/etc/zypp/zypper.conf/main/1/description[2] /files/etc/zypp/zypper.conf/main/1/description[3] = "Default value: autodetected" /files/etc/zypp/zypper.conf/main/1/description[4] /files/etc/zypp/zypper.conf/main/1/description[5] /files/etc/zypp/zypper.conf/main/1/colors = "yes" augtool> Type help for other commands, use TAB key for completion, and check also the Augeas home page for more info. What does this mean for libzypp? Basically the above, with respect to libzypp's files. Currently, you either edit your repos.d/*.repo, locks, credentials, and other files by hand or you leave it to libzypp's frontends, or you at least take care not to write comments in those files, because they will all get removed upon the next change done by libzypp (what we do there is to rewrite the entire files from in-memory data upon saving). This can be easily avoided using Augeas and we can add an editing API for zypp.conf. Plus the bonuses described above. The library package (libaugeas0) would add 300 kiB of installed size to libzypp's/zypper's dependencies, (which is not little), plus an optional 200 kiB of the official lenses (augeas-lenses), if we decide to use them. todo: Look at Augeas' error reporting. The user can of course break the structure of the file in a way that the lens can't map it to the tree anymore. If parsing of the file will fail, we need to report why, so that the user can fix it. - ------copy------ I also have some code using the draft lens for zypper ready, so unless somebody is very much against zypper depending on libaugeas0, i will soon push it. BTW, can i place system-wide zypper.conf to /etc/zypp (the user's will be ~/.zypper.conf). Also, i plan to put the zypper.aug to /usr/share/zypper, so that zypper can tell augeas to read only this .aug file and parse only the zypper.conf files so that it is quick. Whether it's worth to use augeas in libzypp, i propose for discussion. IMO, the effort to enable this is not big, but it is also not a need-to-have, but rather a nice-to-have, and we surely have more important things to do. Just wanted to let you know this is available for grabbing anytime :O) Note that just writing lenses for zypp without touching zypp itself can be beneficial, too. - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmu+u8ACgkQgEhGpmN+6QG4wACeO6t2McWLv8MAjK5A410LFVoi 4zQAnAsaJ/2jvmtiwRaA5DfQ2Xu51suL =oMpW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 5

[zypp-devel] zypper no longer able to install packages from repo?
by Dominique Leuenberger 10 Mar '09

10 Mar '09

Hi, Not sure if I broke something here or if somebody already reported an error alike... that's why I raise it here first. A BNC will follow depending on what goes on here. I have more or less updated my Factory machine to the latest packages (not everything is up to date anymore). So I just wanted to go for it, but zypper up <any package> tells me it can't download: sudo zypper up wol Loading repository data... Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: wol Overall download size: 48.0 KiB. No additional space will be used or freed after the operation. Continue? [YES/no]: Retrieving package wol-0.7.1-137.49.x86_64 (1/1), 48.0 KiB (147.0 KiB unpacked) Retrieving: oss [done] Retrieving: media [done] Retrieving: wol-0.7.1-137.49.x86_64.rpm [error] Failed to download ./suse/x86_64/wol-0.7.1-137.49.x86_64.rpm from http://download.opensuse.org/factory/repo/oss/ Abort, retry, ignore? [A/r/i/?]: a Failed to provide Package wol-0.7.1-137.49. Do you want to retry retrieval? [Factory-OSS|http://download.opensuse.org/factory/repo/oss/] Can't provide file './suse/x86_64/wol-0.7.1-137.49.x86_64.rpm' from repository 'Factory-OSS' History: - Failed to download ./suse/x86_64/wol-0.7.1-137.49.x86_64.rpm from http://download.opensuse.org/factory/repo/oss/ - Can't provide ./suse/x86_64/wol-0.7.1-137.49.x86_64.rpm : Failed to download ./suse/x86_64/wol-0.7.1-137.49.x86_64.rpm from http://download.opensuse.org/factory/repo/oss/ Now the problem is not the file itself, this can be downloaded... from zypper log: 2009-03-10 09:10:09 <1> 3120-2914(11139) [zypp++] MediaManager.cc(checkDesired):116 checkDesired(1): desired (cached) 2009-03-10 09:10:09 <1> 3120-2914(11139) [zypp++] ExternalProgram.cc(start_program):210 Executing '/usr/bin/aria2c' '--user-agent=ZYpp 6.2.2 (aria2 version 1.2.0) ' '--summary-interval=1' '--follow-metalink=mem' '--check-integrity=true' '--file-allocation=none' '--server-stat-of=/var/cache/zypp/aria2.stats' '--server-stat-if=/var/cache/zypp/aria2.stats' '--uri-selector=adaptive' '--use-head=false' '--max-tries=5' '--max-concurrent-downloads=2' '--header=X-ZYpp-AnonymousId: <I am anonymous>' '--header=X-ZYpp-DistributionFlavor:' '--header=Pragma:' '--connect-timeout=180' '--http-proxy=http://<proxy:port>' '--dir=/var/adm/mount/AP_0x00000009/suse/x86_64' 'http://download.opensuse.org/factory/repo/oss/suse/x86_64/wol-0.7.1-137.49.…' 2009-03-10 09:10:09 <1> 3120-2914(11139) [zypp++] ExternalProgram.cc(start_program):354 pid 11204 launched 2009-03-10 09:10:10 <1> 3120-2914(11139) [zypp++] ExternalProgram.cc(checkStatus):401 Pid 11204 exited with status 1 2009-03-10 09:10:10 <5> 3120-2914(11139) [zypp] Exception.cc(log):133 MediaAria2c.cc(getFileCopy):443 THROW: MediaAria2c.cc(getFileCopy):443 : Failed to download ./suse/x86_64/wol-0.7.1-137.49.x86_64.rpm from http://download.opensuse.org/factory/repo/oss/ 2009-03-10 09:10:10 <5> 3120-2914(11139) [zypp] Exception.cc(log):133 MediaAria2c.cc(getFileCopy):467 RETHROW: MediaAria2c.cc(getFileCopy):443 : Failed to download ./suse/x86_64/wol-0.7.1-137.49.x86_64.rpm from http://download.opensuse.org/factory/repo/oss/ 2009-03-10 09:10:10 <5> 3120-2914(11139) [zypp] Exception.cc(log):133 MediaSetAccess.cc(provide):239 CAUGHT: MediaAria2c.cc(getFileCopy):467: Failed to download ./suse/x86_64/wol-0.7.1-137.49.x86_64.rpm from http://download.opensuse.org/factory/repo/oss/ 2009-03-10 09:10:10 <1> 3120-2914(11139) [zypp++] MediaHandler.cc(getDetectedDevices):1387 No devices for this medium 2009-03-10 09:10:10 <1> 3120-2914(11139) [zypp++] MediaSetAccess.cc(provide):249 Media couldn't provide file ./suse/x86_64/wol-0.7.1-137.49.x86 _64.rpm , releasing. Abort, retry, ignore? [A/r/i]: a Problem occured during or after installation or removal of packages: Installation aborted by user Please see the above error message for a hint. By executing the command '/usr/bin/aria2c' '--user-agent=ZYpp 6.2.2 (aria2 version 1.2.0) ' '--summary-interval=1' '--follow-metalink=mem' '--check-integrity=true' '--file-allocation=none' '--server-stat-of=/var/cache/zypp/aria2.stats' '--server-stat-if=/var/cache/zypp/aria2.stats' '--uri-selector=adaptive' '--use-head=false' '--max-tries=5' '--max-concurrent-downloads=2' '--header=X-ZYpp-AnonymousId: <I am anonymous>' '--header=X-ZYpp-DistributionFlavor:' '--header=Pragma:' '--connect-timeout=180' '--http-proxy=http://<proxy:port>' '--dir=/var/adm/mount/AP_0x00000009/suse/x86_64' 'http://download.opensuse.org/factory/repo/oss/suse/x86_64/wol-0.7.1-137.49.…' the downlaod fails as well, but still, not because the file would not exist. The issue is the --dir parameter (/var/adm/mount/AP_0x00000009/suse/x86_64), where the directory does not exist. (I had up to AP_0x00000007, then it failed, I created #8 and after it tried to get the files from #9.. so no joy). By replacing the destination folder, the file downloads perfectly. Anybody seen something alike? (Or even a known bug introduced at some point?) Dominique -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 3

[zypp-devel] What to use as repo alias, if no meaningful string is available...
by Michael Andres 08 Mar '09

08 Mar '09

New in libzypp trunk: static std::string RepoManager::makeStupidAlias( const Url & url_r = Url() ); It will return some stupid string but suitable as alias for your url if nothing better is available. Something like http-download.opensuse.org-83df67e5 or dvd-938d75a0 or repo-a4b57h98 -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 1

Re: [zypp-devel] Augeas for libzypp and zypper?
by Jan Kupec 05 Mar '09

05 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jan Kupec wrote: > Stanislav Visnovsky wrote: >> On Streda 04 March 2009 23:04:31 Jan Kupec wrote: >>> (orignal text at >>> http://jniq.blogspot.com/2009/03/augeas-for-libzypp-and-zypper.html >>> reposting for discussion) >>> >>> ------copy------ >>> The need for a configuration file for zypper (plus my wish for a nice >>> CLI for handling it) and a visit to Raphaël Pinson's presentation at >>> FOSDEM made me look at Augeas closely. >>> >>> Augeas enables you to read and edit your config files in a way which >>> preserves comments and formatting details, allowing humans and programs >>> coexist peacefully when it comes to editing configuration files. More >>> than that, you can map some special structures of the file to special >>> parts of the augeas tree, rather than using the generic INI file parser. >>> See the zypp.conf for example (zypper.conf will have the same structure): >>> >>> >>> [main] >>> ## Option description. >>> ## Default: etc. >>> ## >>> # disabledoption = value >>> >>> ## Another option description >>> ## >>> >>> another.option = value >>> >>> >>> >>> With Augeas you can write a lens (the file contents description) which >>> will map such file into a tree like this: >>> >>> >>> /files/etc/zypp/zypp.conf/main/1 >>> /files/etc/zypp/zypp.conf/main/1/description[1] = "Option description." >>> /files/etc/zypp/zypp.conf/main/1/description[2] = "Default: etc." >>> /files/etc/zypp/zypp.conf/main/1/description[3] >>> /files/etc/zypp/zypp.conf/main/1/commented >>> /files/etc/zypp/zypp.conf/main/1/disabledoption = "value" >>> /files/etc/zypp/zypp.conf/main/2 >>> /files/etc/zypp/zypp.conf/main/2/description[1] = "Another option >>> description." >>> /files/etc/zypp/zypp.conf/main/2/description[2] >>> /files/etc/zypp/zypp.conf/main/2/another.option = "value" >>> >>> >>> >>> Note the commented node. Augeas has an API for looking for the nodes, >>> getting values from them, setting the values, and finally saving the >>> tree back to the config file. >>> >>> What does this mean for zypper? Implementing zypper conf --list is a >>> piece of cake, as well as zypper conf --set another.option value. >>> Commenting or uncommenting the option is a matter of adding or removing >>> the commented node. Getting the option description for zypper conf >>> --help some.option is easy (and maybe it is possible to map the >>> multi-line ## description to a single 'description' node!). >>> >>> Here is a draft of lens for zypper (it will need comments and further >>> improvements). To try it out you can crete a /etc/zypp/zypper.conf file >>> with contents like the above example, and use the augtool like this: >>> >>> $ augtool -I /the/dir/with/the/zypper.aug/file >>> augtool> print /files/etc/zypp/zypper.conf/ >>> /files/etc/zypp/zypper.conf >>> /files/etc/zypp/zypper.conf/anon >>> /files/etc/zypp/zypper.conf/anon/description[1] = "Configuration file >>> for zypper" >>> /files/etc/zypp/zypper.conf/anon/description[2] >>> /files/etc/zypp/zypper.conf/anon/description[3] = "Boolean values are 0 >>> 1 yes no on off true false" >>> /files/etc/zypp/zypper.conf/main >>> /files/etc/zypp/zypper.conf/main/1 >>> /files/etc/zypp/zypper.conf/main/1/description[1] = "Whether to use colors" >>> /files/etc/zypp/zypper.conf/main/1/description[2] >>> /files/etc/zypp/zypper.conf/main/1/description[3] = "Default value: >>> autodetected" >>> /files/etc/zypp/zypper.conf/main/1/description[4] >>> /files/etc/zypp/zypper.conf/main/1/description[5] >>> /files/etc/zypp/zypper.conf/main/1/colors = "yes" >>> augtool> >>> >>> >>> >>> Type help for other commands, use TAB key for completion, and check also >>> the Augeas home page for more info. >>> >>> What does this mean for libzypp? Basically the above, with respect to >>> libzypp's files. Currently, you either edit your repos.d/*.repo, locks, >>> credentials, and other files by hand or you leave it to libzypp's >>> frontends, or you at least take care not to write comments in those >>> files, because they will all get removed upon the next change done by >>> libzypp (what we do there is to rewrite the entire files from in-memory >>> data upon saving). This can be easily avoided using Augeas and we can >>> add an editing API for zypp.conf. Plus the bonuses described above. >>> >>> The library package (libaugeas0) would add 300 kiB of installed size to >>> libzypp's/zypper's dependencies, (which is not little), plus an optional >>> 200 kiB of the official lenses (augeas-lenses), if we decide to use them. >>> >>> todo: Look at Augeas' error reporting. The user can of course break the >>> structure of the file in a way that the lens can't map it to the tree >>> anymore. If parsing of the file will fail, we need to report why, so >>> that the user can fix it. >>> ------copy------ >>> >>> I also have some code using the draft lens for zypper ready, so unless >>> somebody is very much against zypper depending on libaugeas0, i will >>> soon push it. BTW, can i place system-wide zypper.conf to /etc/zypp (the >>> user's will be ~/.zypper.conf). Also, i plan to put the zypper.aug to >>> /usr/share/zypper, so that zypper can tell augeas to read only this .aug >>> file and parse only the zypper.conf files so that it is quick. >> I'm still not sure if 300kiB of a library for reading a INI file is worth it. > > For reading certainly not :O) For the other stuff, maybe. For the sake of accuracy, it is 220k on 32 bit archs :O) Those 300k are on 64 bit. - -- cheers, jano -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmv9aYACgkQgEhGpmN+6QH6CgCeKtMICcfgTwQaJXpvXXVZXE1U hmAAni3LhdygbjPuO0l0/rHNGNP9viJN =9tkz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0