Re: [gentoo-amd64] Re: kdepim 3.5.7 & kpilot 3.5.5

[Beso]

why not just unmask the 3.57 kpilot and try to see if it builds?!

2007/10/19, Duncan <1i5t5.duncan@×××.net>:
>
> alain.didierjean@××××.fr posted 1192705442.47173da233e93@××××××××.fr,
> excerpted below, on  Thu, 18 Oct 2007 13:04:02 +0200:
>
> > Any known way to make kdepim 3.5.7 & kpilot 3.5.5 work together ? It
> > seems that kpilot 3.5.7 has a low priority and some bugs left. kpilot is
> > not included anymore in kdepim and trying to install the latter after
> > installing kpilot 3.5.5 leads to emerge vows:
>
> [snipped blockage list]
>
> Have you tried emerge --nodeps ?  That might do it.  What I'd try first
> would be merging the new kdepim-meta, then seeing if the old kpilot will
> build against it (using emerge --nodeps =kpilot-3.5.5).  If it will,
> great.
>
> Otherwise, you may have to remerge the old kdepim-meta, use quickpkg (if
> you don't have binary packages built automatically with
> FEATURES=buildpkg) to binpkg-up the old kpilot, remerge the new kdepim-
> meta, then emerge --nodeps --usepkgonly =kpilot-3.5.5.  That should merge
> it fine, since you are merging the binpkg version of it so there can't be
> any build issues, but it's somewhat of a crapshoot of whether it'll
> actually work or not, since it would be built against the old kdelibs and
> kdepim, not the new ones now merged that it'd be trying to run against.
>
> HTH.  I don't have (nor do I really need) a handheld, so while I use KDE,
> I don't have kpilot installed at all and know little about it.  However,
> I'm a bit more familiar with portage, and have used the --nodeps switch
> myself on occasion, as well as regularly using my favorite power-user
> feature of portage, FEATURES=buildpkg, and the packages it builds as a
> result.
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
> --
> gentoo-amd64@g.o mailing list
>
>


-- 
dott. ing. beso