Intalling non-portage apps

[Brandon]

If I just have some source and a makefile, how does the Portage system handle me mucking with its files? Since Portage seems to involve calling make and configure like normal at some step behind the scenes, it stands to reason that there's some way to make it install something that's not an .ebuild, but the documentation didn't mention it that I saw.

Also, come to think of it, what happens if I install a new version of an application that IS part of portage because I was too eager to wait for it to become part of the tree. Would that break something?

[delta407]

You can install stuff whatever you like onto your system; Portage doesn't care. Portage will not install files that are not ebuilds or were not generated by Portage (from an ebuild originally). So, if you want easy install/uninstall capabilities, I would suggest writing an ebuild.

Also, Portage won't know about your manually installed package if something else requires it. (There's always --inject, but that's mean.) Just FYI...
_________________
I don't believe in witty sigs.

[Oyarsa]

Check this out.
_________________
Dew knot trussed yore spell chequer two fined awl ewer miss steaks.