[PALUDIS] Support thread (current v. 0.26.*) - Part 4

[cerebro84]

[cerebro84]

[cerebro84]

Thanks for the hint however, I solved by manually setting its SLOT (the file was empty!)

[slycordinator]

Since my command didn't work (and it fell back to the installed version) that makes me think you've made

[cerebro84]

I didn't change paludis default options

[slycordinator]

[cerebro84]

Thanks a lot, all solved, I'm starting to like paludis

[Finswimmer]

I thought Paludis does not need creating a Manifest (that was ebuild *.ebuild used to do)?
But I copied an ebuild to a higher date and now it fails:

[franzf]

[Berniyh]

[cerebro84]

Hi,
this is what I get when I try to install docutils:

[vetienne]

Hello,

i try to build a arm cross complier but when i "emerge" the compiler with
contraius -t arm-unknown-linux-gnu -s full
it always failed with "No versions of 'cross-arm-unknown-linux-gnu/binutils' are available"
unless i first do crossdev -t arm-unknown-linux-gnu

How should i use it (if i still need crossdev -t what's the point of contrarius) ?

A second question :
i need to setup a minimal binary image so with emerge normally
First, emerge in /usr/arm-unknown-linux-gnu first with a ROOT=/usr/arm-unknown-linux-gnu and xmerge script file with setup arch and so on
Second, rebuild it in a second root ( say /image with ROOT=/image and INSTALL_MASK to avoid man pages, include headers file, ... )

I have try to setup a specpath.conf
- first one is arm with root=/usr/arm-unknown-linux-gnu : ok work like emerge
- second one with root=/image : root is not use like only the target destination but like achroot root => end up with a copy of /usr/arm-...

To circumvent the problem, for the moment i have mounted ( mount -o bind ) /etc/paludis from usr/arm root in /image root and the same for /usr/include, /usr/share, /var/cache and some other directory. Seems more or less equivalent but a bit complex ( and likely to produce problem : not sure i have not forget a link so my image could have more files than needed... )

Someone has some experienced with this and could perhaps help me ?

[creidiki]

[slycordinator]

[cerebro84]

[zxy]

[slycordinator]

How did you enable collision protection to begin with then?

[cerebro84]

I didn't. It was already enabled, and I'm sure it wasn't imported by the script from portage configuration because I disabled it there...

[creidiki]

You're all barking up the wrong tree.

That 'sanity check' stuff has nothing to do with dleverton's collision-protect hook.
_________________
'((eINIT) (soor overlay))

[slycordinator]

That's what I was alluding to. Collision protection is NOT enabled (or even existent to be enabled) by default.

And you should definitely not disable sanity checks

[radum]

When I try

[creidiki]

The package changed name from x264-svn to x264.

Reinstall ffmpeg to update the relevant dependency block to the one currently in portage, which uses the correct package name.

Hint: in these cases 'paludis -qD package' (to look at deps of installed version) followed by 'paludis -qD cat/pkg::repo' (to look at deps of tree ebuild) is invaluable for debugging this kind of issue.
_________________
'((eINIT) (soor overlay))

[cerebro84]

[wobble]

[slycordinator]

So every time a new binutils or gcc is released you have to copy the ebuilds to your other repository?