[KDE/Mac] macports taglib-devel uses https://svn.kde.org instead
Orville Bennett
illogical1 at gmail.com
Fri Mar 6 22:11:10 CET 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mar 5, 2009, at 10:07 PM, Andrew Stromme wrote:
> Whoops, looks like I was overzealous. Sorry for that :(
>
> I dug around some more and found that it's probably an artifact of
> the way my
> system is set up. It's a shared machine that mounts the home
> directories via
> nfs. Additionally, the home dirs are of the type /home/$classyear/
> $username
> rather than the traditional /home/$username. Also, it seems like a
> sudo'd user
> is unable to access said directories.... the following commmand
> fails on dir
> not found:
>
> sudo ls $HOME
>
> (where $HOME points to /home/$classyear/$username)
>
> What this means is that the $HOME/.subversion conf dir can't be
> created/read
> when the "sudo svn blah" commands are given. This means that I can't
> save the
> "permanently remember this server" option.
>
> Is there any way to override this? Why does amarok depend on taglib-
> devel and
> not plain old taglib?
Because I made it so!
You can change this by using the 'port edit $portname' command should
you desire.
Taglib from svn seems pretty stable and built without any trouble
using gcc4.2 so I used that.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkmxkW4ACgkQ2yWVgjgEOKQSPACaAwuDRHcAgF/f1d7bvMkpb9Kr
45gAnRIkEuBKtyGRlgOtgVinmrP4H1th
=wBHz
-----END PGP SIGNATURE-----
More information about the kde-mac
mailing list