Welcome, Guest. Please login or register.
April 21, 2014, 06:36:14 AM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

  Show Posts
Pages: [1]
1  Assistance / Configuring Pardus / Re: How resource hungry is KDE 4? on: July 08, 2009, 12:56:57 PM
I actually ran kdemod kde4 on Asus EEEpc 701 (the original prerelease model).

It's a bit sluggish, but it works Tongue

(KDE4 is more resource hungry than KDE3, but if you turn off background services like nepomuk and strigi, it's much more bearable)
2  Assistance / Bugs / Re: lzma is not statically linked on: May 04, 2009, 14:39:30 PM
Lzma is still not statically linked, so the thread is probably not solved, but I filed it to bugtracker instead, so i will close it here in the forum.
3  Assistance / Bugs / Re: lzma is not statically linked on: April 28, 2009, 09:28:42 AM
For now fix was to grab statically linked lzma from http://tukaani.org/lzma/download and reinstall gcc from a pisi package. Phew!
4  Assistance / Bugs / [solved] lzma is not statically linked on: April 27, 2009, 22:53:37 PM
Upgrading to new upstream version
Configuring gcc package for removal
Extracting the files of gcc
System Error. Program Terminated.
lzma: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

I think packages used for pardus maintenance should have statically linked versions to be fully independent of however complex upgrades/downgrades of the system they manage. I downgraded gcc but forgot to downgrade libgcc, now I cannot re-upgrade gcc because of missing libstdc++.so.6
5  Assistance / Pardus for beginners / Re: Building packages with PiSi on: April 26, 2009, 12:24:10 PM
What I ultimately need is a gcc-4.4.0 package, but it looks like it's a big task, with all those patches.
6  Assistance / Pardus for beginners / Building packages with PiSi on: April 26, 2009, 11:22:34 AM
Building PiSi source package: gcc
Safety switch: system.devel is already installed
PartOf tag not defined, looking for component
System Error. Program Terminated.
Cannot find component.xml in upper directory

Umm, this is quite confusing. What are this Safety switch and PartOf things and what does it mean?
7  Assistance / Bugs / Re: Skype on: April 23, 2009, 04:29:01 AM
Good howto, thanks!
8  Assistance / News & Announcements / Re: Pardus 2009 on: April 22, 2009, 12:07:15 PM
One more thing: developers, developers, developers.

I understand that Pardus is mainly a user distro, but having many development tools avaliable is crucial. Latest svn, bzr, git, waf, kdevelop4, llvm (I was surprised, but pardus has llvm in repos, yay!), gcc, ruby, rubygems, python 2.6, and many more things needed for developers are a good thing - it makes developing on the system easier and attracts more people who can develop more good software and actually install it on the system.


I like the systematic approach of Pardus developers - a clear release roadmap is great to have.

Another thing I want to see easier is making your own pisi packages. Some packages are available as binary only and search in source repository doesn't find them - makes us users unable to modify and try out different versions (sometimes a simple version bump is enough, when you have the source pspec.xml file) - I would like to see developers committing their build recipes to pardus svn, either main or some contrib sources repo - didn't find this one yet, does it exist? We should be able to quickly find a source recipe for any binary package in the added repos. IDEA: add some chainlink from the binary repos to source repos, so you don't even have to add source repos manually.

I want to be able to create new recipe as easy as possible.
Verbose XML format is good, but it's tedious to write (and PisiYap failed to work for me, for reasons unknown it just doesn't generate any files).
I like GoboLinux recipes - they are declarative, don't require almost any programming for 99,99% of common cases - so recipes for new packages end up being one or two lines - URL of source package and type of build system to use - and this is extremely important when you want to gain some new packages. While Pardus is far from this Zen style recipes, using a less complex format might be good, for example adding support for YAML instead of XML should be relatively easy and remain compatible with old XML based packages, while allowing to write new pspec files in a simple human-friendly format.
9  Assistance / News & Announcements / Re: Pardus 2009 on: April 22, 2009, 08:30:07 AM
Improve pisi:

1. Use nicer output for pisi ls - similar to gentoo's eix or arch's yaourt:
repo/package-name  version  (installed version)
  - Description
Use colors, e.g. installed version is green if ok or yellow if upgrade is available.

2. Do not depend on order of repositories, but use versions instead to determine if upgrade is needed. Having to reshuffle repos to get upgrades from test didn't look like an intuitive operation.

3. Do not show me the same package from different repos twice (listing same packages from pardus-2008.2 and pardus-test doesn't give any advantage).

4. Do not stall graphical pisi frontend for 3 seconds every time I select a package for install or uninstall. Of course, it needs to calculate dependencies, but there is multithreaded programming and other technologies developed. When I uninstalled several pkgs using graphical frontend it was mostly a blind shooting - click several
  • and wait some time till they all get unchecked.
Pages: [1]

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!