Paludis support thread (current v. 0.14.3) - Part 1

[zxy]

PALUDIS SUPPORT THREAD

[mod]This thread has now been locked as it's here for historical purposes. The discussion has moved to the Paludis support thread (current v. 0.16.0) - Part 2 - Jorge (jmbsvicetto).[/mod]

• ABOUT
  
  Paludis is a portage alernative.
  
  I created this thread for everybody that has problems with using paludis or has something useful to contribute to others about paludis.
  
  Paludis is different than portage in command line and configs differ, too.
  
  Any help, info, shortcut, howto or a tip is welcome here.
• LINKS
  
  (links changed - UPDATED)
  
  The link to paludis homepage: http://paludis.pioto.org/
  
  Migration from portage to paludis howto: http://paludis.pioto.org/migration.html
  
  WIKI: http://gentoo-wiki.com/HOWTO_Use_Portag ... _-_Paludis
  
  You can also find some information abot Paludis on Ciaran McCreesh's Web Thingy. Usualy he anounces new versions and describes what's new.
  
  
  NEW: paludis-extras overlay
  Now includes:
  • paludis-hooks-0.1.7 -- hooks by truc, dleverton, zxy and other possble contributors
  • portage-utils--20070118 (paludis version) -- truc
  • gentoolkit-20061127 (revdep-rebuild modified for paludis) -- jordan83
  Install instructions and change logs are here: Paludis - scripts
  where you can also find some of the scripts from this thread.
  This overlay is unsupported by gentoo and paludis devs. Do not bother them about it. You can ask questions on this thread.
• INSTALLATION
  
  Paludis is now in portage, at the time of this writing version 0.14.3 is available in ~arch. For migrating see the guide in the links section.
• KNOWN ISSUES - DIFFERENCES BETWEEN PORTAGE AND PALUDIS
  
  If you encounter any problems read the docs on Paludis homepage. One of them is http://paludis.berlios.de/KnownIssues.html
  To my knowledge the link is not available any more.
  You can see the FAQ page here: http://paludis.pioto.org/faq.html
  
  Check HERE: http://paludis.pioto.org/portagedifferences.html to read about differences between portage and paludis.
  
  There is many things in this thread, too. And don't forget the wiki.
• THIS THREAD AND WIKI INCLUDE
  
  In this thread and in the wiki you can find how to make the following work with Paludis:
  • eix
  • revdep-rebuild
  • ccache
  • portage-utils
  • zsh scripts
  • hooks
    • [post=3819343]manage orphaned files after unmerging; for prelinked libraries[/post] - 2007-01-05 (by dleverton)
    • [post=3785412]collision-protect[/post] - 2007-01-04 (by dleverton)
  • various tips, tricks, Q & A
  and more...

Enjoy using Paludis,
zxy


It is NOT alowed to start FLAMEWARS here. Go to other threads if you search for a fight!!!!!
For fights go here for example:
http://forums.gentoo.org/viewtopic-t-49 ... ight-.html
and there are many more there on the forums.

[xoomix]

From the website you posted:

"...Warning:
Do not file bugs related to Paludis on Gentoo Bugzilla. Do not discuss Paludis on Gentoo mailing lists or forums."

[zxy]

@xoomix Added to the first post.

---------------------------------------

After a migration I was receiving some warnings about my overlays.
I had to create a file /usr/local/portage/profiles/repo_name and put the name of the repository in it

Code: Select all

#nano  /usr/local/portage/profiles/repo_name
local_portage

or any name you want to use for this repository.

My LDFLAGS were not moved from make.conf to paludis, too. So I had to add them to /etc/paludis/bashrc
I added a new line:

Code: Select all

export LDFLAGS="-Wl,-O1 -Wl,--hash-style=both -Wl,--sort-common -s"

[zxy]

for using ccache use

Code: Select all

export PATH="/usr/lib/ccache/bin:$PATH"
export CCACHE_DIR="/var/tmp/ccache/"
export CC="ccache gcc"

-----------------

instead of

Code: Select all

emerge -e world

is this

Code: Select all

paludis -i world --dl-reinstall always

[ciaranm]

MY OPINION
On the paludis site is this

Warning:
Do not file bugs related to Paludis on Gentoo Bugzilla. Do not discuss Paludis on Gentoo mailing lists or forums. Do not pester Gentoo developers about Paludis. Read the known issues list.

Yeah, I'm going to tone that down for 0.10. When that was written Paludis wasn't in the tree. Now it is.

[jordan83]

Hi,

A couple of questions:

1) How do I perform a generic search with Paludis? The -q option is not really powerful:

altair ~ # paludis -q mail
paludis@1164183114: [QA] Couldn't open repo_name file in '/usr/local/portage/profiles/'. Falling back to a generated name.

Query error:
* In program paludis -q mail:
* When performing query action from command line:
* When handling query 'mail':
* When disambiguating package name 'mail':
* Could not find 'mail'

Portage finds 109 ebuilds that fit the "mail" word.
Is it possible to use eix when using Paludis?

2) Is there any equivalent command to perform the work done by revdep-rebuild?

Thanks

[BlackEdder]

I also have a general question:
Is there a emerge --depclean like option?
Is something like ELOG supported?
And I am also very interested in the revdep-rebuild question

[truc]

Hi,

A couple of questions:

1) How do I perform a generic search with Paludis? The -q option is not really powerful:

altair ~ # paludis -q mail
paludis@1164183114: [QA] Couldn't open repo_name file in '/usr/local/portage/profiles/'. Falling back to a generated name.

Query error:
* In program paludis -q mail:
* When performing query action from command line:
* When handling query 'mail':
* When disambiguating package name 'mail':
* Could not find 'mail'

Portage finds 109 ebuilds that fit the "mail" word.
Is it possible to use eix when using Paludis?

2) Is there any equivalent command to perform the work done by revdep-rebuild?

Thanks

1)

• I've made a patch for portage-utils so that it support overlay, it's on bugzilla [bug]154405[/bug] Only portage users will use this since there is almost nothing about paludis in the bug report (as requested on the paludis homepage)
  
  So, I made an ebuild for every one:
  Here it is : portage-utils-20061217.ebuild
  Again every one can use it, but paludis users will add app-portage/portage-utils paludis to their use.conf
  (note that, with the changes I made, qlop is better with paludis than with portage )
  
  You DON'T have to download anything, but the ebuild, since it will do the job for you
  
  here is the french thread where I explain my changes in portage-utils. But for every one here is a short sumary:
  • qcache: you can still use it but you now also have adjuctrix with paludis
    
    q:
    • the big change is the overlay support, I change the syntax of the .ebuild.x file, q -ls-overlays to see your overlays
      Note that the name of the overlay is taken in the $overlay_dir/profiles/repo_name) and if it doesn't exist, the name is "filename($overlay_dir)" for portage and x-filename($overlay_dir)"for paludis (since paludis does this) (e.g.: jordan83, your local overlay name is x-local since their is no "profiles" directory into it (with the categories and repo_name files (you can see that with paludis --list-repositories))
    qlop
    • nothing change for portage users. paludis users will have an almost useless --overlay option, to search the log for package installed from a repository (or to search the last syncs for a given repo.. kind of useless, but who knows )
      The --current option also shows the overlay where the package, being installed, is from, but again that's only for paludis users
    quse, qgrep, qsearch:
    • possibility, to search for a flag meaning, to grep , and to search , in every overlay or just the one you want with the --overlay option (and the name given with q -l )
      As I already said elsewhere, this can be handy to accelerate searching if you already know where to search, or the 'greping' only grep in a overlay..
      An other interesting point is when you have a new overlay, you may want to have an idea what's into it:

      Code: Select all

      qsearch --overlay new_overlay_name -a

      will print the description of every package from that overlay, We can do the same with quse.
      Note that overlay can have their own profiles/use.{,local}.desc and profiles/desc/*, quse will search through all these files (or just those of a given overlay with the --overlay option)
      Also note that I've added a functionnality to have something like equery uses which describes every flag of a given package, by default, quse --all -vv would describe every flag for every package (for every overlay) but I've added the possibility to make something like this work (it's not perfect, but it's enough I think)

      Code: Select all

      quse -a ludis-scm orrent-stats -vv
      gentoo::net-p2p/bittorrent-stats/bittorrent-stats-3.2.1b-r4.ebuild X
       global:X: Adds support for X11
      paludis-overlay::sys-apps/paludis/paludis-scm.ebuild doc pink selinux qa ruby glsa
       global:doc: Adds extra documentation (API, Javadoc, etc)
       local:pink:sys-apps/paludis: Use a less boring colourscheme than the default
       global:selinux: !!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur
       local:qa:sys-apps/paludis: Enable QA tools.
       global:ruby: Adds support/bindings for the Ruby language
       local:glsa:sys-apps/paludis: Enable parsing of GLSA files 

      (just try it, cause it's ugly without colors)
      
      note(I think I love this word yeah..) that the output of qsearch allow some handy copy and paste for paludis:

      Code: Select all

      qsearch -s portage-utils
      app-portage/portage-utils::gentoo small and fast portage helper tools written in C
      app-portage/portage-utils::local small and fast paludis helper tools written in C
      

      we can now copy and paste app-portage/portage-utils::local directly to paludis and it will emerge (?) the right package for you
      
      And the last thing I can think of right now, is an other option I've added to qsearch: -p, --show-path * Show the path to the ebuild
      because otherwise I missed my esearch -e
    every other q tools work as before.
    Of course, if you find something you don't like don't post on bugs.gentoo.org, since they don't have anything to do with that yet. (but you can still add a comment on the bug report, saying that's great ) Just say it there, or pm me for that.
  
  
  
  
  
  
  ================================
  
  I've been also asked about eix, so here is what you can do for the moment:
• create the profile link as we used to do with portage (/etc/make.profile)
• create a basic make.conf ( e.g.: [ code ]echo -e "PORTDIR="/var/paludis/repositories/gentoo"\nPORTDIR_OVERLAY="/var/paludis/repositories/local /var/paludis/repositories/initng /var/paludis/repositories/einit /var/paludis/repositories/paludis-overlay"" > /etc/make.conf[/code] don't copy &paste blindly ! )
  To update eix cache just run update-eix (cf man eix, if you want to play with this cache file, make the diff (to have something like the output of eix-sync -v ..))
  There is a better way, check this
  
  But you can't restrict you search on an overlay with eix, wheras you can do it with qsearch (but eix is a lot quicker when it comes to search the DESC.. )

[Earthwings]

Moved from Portage & Programming to Unsupported Software - see [post=3734803]this post[/post] for details. Short: The paludis ebuilds are in Portage and support threads about the ebuild failing to install paludis should be posted in Portage & Programming. Support questions about paludis and its (mis)behaviour go into Unsupported Software unless the Gentoo council decides that paludis is a supported package manager by Gentoo.

[zxy]

I have a question about overlays. I wanted to use nxty's glibc/binutils overlay, but I cant make it work.

1. I copied the overlay to /usr/local/overlays/toolchain_overlay/ using

Code: Select all

svn co ......

2. I added profiles folder with repo_name.

I get this when I want to

Code: Select all

 # paludis -i binutils
Building dependency list... done

These packages will be installed:

* sys-devel/binutils-2.17.50.0.6::toolchain_overlay [S] multislot (-multitarget) nls -test -vanilla

Total: 1 package (1 in new slot)


Installing sys-devel/binutils-2.17.50.0.6::toolchain_overlay

paludis@1164242083: [WARNING] No thirdpartymirrors file found in '/usr/local/overlays/toolchain_overlay/profiles', so mirror:// SRC_URI components cannot be fetched

Install error:
  * In program paludis -i binutils:
  * When performing install action from command line:
  * When executing install task:
  * Install error: Can't install 'sys-devel/binutils-2.17.50.0.6' since SRC_URI references unknown mirror:// 'kernel'

Resume command: paludis --log-level qa --dl-installed-deps-pre discard --dl-installed-deps-runtime discard --dl-installed-deps-post discard --dl-uninstalled-deps-pre discard --dl-uninstalled-deps-runtime discard --dl-uninstalled-deps-post discard --install --preserve-world =sys-devel/binutils-2.17.50.0.6::toolchain_overlay

What to do next?



@Earthwings At least it's not in Off the Wall

[kreedcarmoch]

Is there a emerge --depclean like option?

paludis --uninstall-unused is available in the current svn. I haven't tried it yet, but it sounds like it should do the trick.

Is it possible to use eix when using Paludis?

Yes, just make sure the eix cache method is set to metadata and the PORTDIR and PORTDIR_OVERLAY in make.conf settings are correct.

[Phenax]

How do I digest an ebuild using Paludis?

[zxy]

I just used

Code: Select all

ebuild xxxxxxx.ebuild digest

.

[Phenax]

I just used

Code: Select all

ebuild xxxxxxx.ebuild digest

.

That's part of portage if I understand, Paludis -- being an alternative to portage I was hoping had an ebuild digesting tool.

[truc]

...

Either copy blindly the thirdpartymirror file from gentoo/profiles/ to local/profiles, or create a similar file with only what you need.

[ciaranm]

I just used

Code: Select all

ebuild xxxxxxx.ebuild digest

.

That's part of portage if I understand, Paludis -- being an alternative to portage I was hoping had an ebuild digesting tool.

Nope. We'll have a digest creating tool when the new signed manifest format is agreed upon. Until then there's no point.

[zxy]

@ciarnm
1. Is it possibe to add a short option for updating. As I have found out by now I have to use

Code: Select all

paludis -i world --dl-reinstall always

or

Code: Select all

paludis -i world --dl-reinstall if-use-changed

Is there a shorter version already? I've got quite used to one letter options that I use almost every day.

2. Where to get a gui app, I saw on your site, that is like a frontend for paludis.

[ciaranm]

@ciarnm
1. Is it possibe to add a short option for updating. As I have found out by now I have to use

Code: Select all

paludis -i world --dl-reinstall always

or

Code: Select all

paludis -i world --dl-reinstall if-use-changed

Is there a shorter version already? I've got quite used to one letter options that I use almost every day.

We keep on discussing this. Unfortunately we're running out of letters... So, for now...

Either export PALUDIS_OPTIONS="--stuff-you-want" or make yourself some shell aliases.

If I had a decent idea of which options people most frequently use, I'd be more confident allocating those oh so precious short option letters...

2. Where to get a gui app, I saw on your site, that is like a frontend for paludis.

gtkpaludis is disabled in released tarballs. In svn it's available via --enable-gtk. Note that it's nowhere near complete or usable -- for example, clicking on the Install button doesn't do anything. The hard stuff (figuring out the thread model) is done; hooking up all the clicky things isn't.

If anyone's familiar with gtkmm, contributing to gtkpaludis wouldn't be hard. It'd be fine by me if someone wanted to take over the easy stuff and leave the weird tricky bits to me... That's more or less what's happened with the Ruby interface.

[jordan83]

I have a problem to install the portage-utils ebuild provided by truc.
The steps I've done are in continuation:

1) Created /usr/local/portage/app-portage/portage-utils/
2) created files dir inside 1)
3) "wgetted" the ebuild into 1)
4) cd /usr/local/portage/app-portage/portage-utils/ && ebuild portage-utils-20061122.ebuild digest which exited successfully

After an "update-eix" I had this:

Code: Select all

app-portage/portage-utils
     Available versions:  0.1.20 ~0.1.21 ~20061122[1]
     Installed:           0.1.20
     Homepage:            http://www.gentoo.org/
     Description:         small and fast paludis helper tools written in C

[1] /usr/local/portage

Unluckily trying paludis -q portage-utils the new ebuild wasn't listed.

I thought it was a problem of "syncing" the repository and I tried:

Code: Select all

paludis --sync

During syncing process I saw that repository "x-portage" was skipped. I changed my /etc/paludis/repositories/portage.conf file from this:

Code: Select all

location = ${ROOT}/usr/local/portage
sync =
profiles = ${ROOT}/usr/portage/profiles/default-linux/x86/2006.1/desktop
eclassdirs = /usr/portage/eclass
distdir = ${ROOT}/usr/portage/distfiles
cache = /var/empty
format = portage

to this:

Code: Select all

location = ${ROOT}/usr/local/portage
sync = file://${ROOT}/usr/local/portage
profiles = ${ROOT}/usr/portage/profiles/default-linux/x86/2006.1/desktop
eclassdirs = /usr/portage/eclass
distdir = ${ROOT}/usr/portage/distfiles
cache = /var/empty
format = portage

(note sync = line!)

I tried then:

Code: Select all

paludis -s portage

and finally the local repository has not been skipped.

But, unluckily, the portage-utils-20061122.ebuild is still missing

was the change I made to /etc/paludis/repositories/portage.conf necessary?
What am I doing wrong? How can I install portage-utils?

The last question I want to ask is this:
Where can I find qualudis to do revdep-rebuild's work? Is this tool ready to use?

Thanks again!

P.S. As kindly stated by zxy it would be nice if you all stop to light the fire and start discussing in love and peace with us to let Gentoo become a even better distribution and to keep Gentoo Forums a friendly place...
Please, you all use another thread to fight since I'm quite interested in Paludis and I'd like to have the freedom to try it and discuss about it

[ciaranm]

Where can I find qualudis to do revdep-rebuild's work? Is this tool ready to use?

Qualudis is a QA tool. It doesn't have anything like revdep-rebuild's functionality.

For now, we suggest that you use find, ldd and paludis --owner, as people did in the good old days. It would be easy enough to script, if anyone's that way inclined...

[Bapt]

@jordan83 : did you fill your /usr/local/portage/profiles/categories whith app-portage ?
by the way you should had, if it's not done : /usr/local/portage/profiles/repo_name with the name "portage" in it.

[ciaranm]

@jordan83 : did you fill your /usr/local/portage/profiles/categories whith app-portage ?

Lack of a categories file is a warning these days. If the file's not there, Paludis gets the categories list by looking at all subdirectories that're valid category names.

If the file's there and incomplete you'll have issues...

[jordan83]

You are right.
I have categories file but the app-portage was missing

By the way, was the change I made in /etc/paludis/repositories/portage.conf to sync line necessary?

A few comments I'd like to share:
- I agree with zxy about having "short" switches, at least for common tasks
- Paludis does not change correctly console's title bar after installation has finished (it keeps "(x of y) Cleaning bbb-hhh/aaaaaa" ) (tiny bug report)
- parallel-fetch feature would be appreciated, especially by people with slow connections
- I don't really agree with the choice of not implementing "wget resume support"... In my opinion this feature is really useful ( I think many people with slow connections - like me - like it in Portage). I think you should leave this feature optional, not completely disabled.

I must say that Paludis is getting every day more interesting
Keep on developing it!

[ciaranm]

- I agree with zxy about having "short" switches, at least for common tasks

Find a list of common tasks and convince me it's genuine.

- Paludis does not change correctly console's title bar after installation has finished (it keeps "(x of y) Cleaning bbb-hhh/aaaaaa" ) (tiny bug report)

I'm still arguing that that one's not a bug. There's no sane way of getting what the console title is, so it can't restore it. Most people (and most programs that use this feature) rely upon their shell resetting the title via, for example, PROMPT_COMMAND.

Now, it just so happens that Portage has a reaallllllly dirty hack whereby it sets the title to what used to be the Gentoo default title string upon exit, which is why most people don't notice this. If you change your title and don't use PROMPT_COMMAND, however, you'll get a screwed up title on exit with this.

- parallel-fetch feature would be appreciated, especially by people with slow connections

Wouldn't it be of more use for people with fast connections?

- I don't really agree with the choice of not implementing "wget resume support"... In my opinion this feature is really useful ( I think many people with slow connections - like me - like it in Portage). I think you should leave this feature optional, not completely disabled.

Submit a patch.

[truc]

- parallel-fetch feature would be appreciated, especially by people with slow connections

Wouldn't it be of more use for people with fast connections?

I think, by parallel-fetch he meant, downloading packages while an other is being compiled.


jordan83 I, actually, have no sync line in my local overlay configuration file