Pardus 2009

[berkus]

Improve pisi:

1. Use nicer output for pisi ls - similar to gentoo's eix or arch's yaourt:

Code:

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.

[Michiel]

I agree with all of these suggestions, good points.
Especially the delay upon checking or unchecking packages is sometimes quite annoying

[berkus]

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.

[rocky2]

And do not make KDE4 as default desktop environment!!! PLEASE! Leave it on KDE3! ))

I absolutely agree, please stay with KDE3!!

Yes ! I absolutely agree, please stay with KDE3 !! 

[bubbel]

Hello together,

look please in this Thread

You can stay with KDE3, if you work further with Pardus 2008.2  

Greetings
bubbel