Bugzilla Bug 25805

From author's site:

Soapbox allows to restrict processes to write only to those places you want.
Read-access however is still based on file-permissions. By preloading the
Soapbox library, you can run programs as root and monitor which writes/changes
are made, without them really happening. (Typically 'make install')

Reproducible: Always
Steps to Reproduce:

Created an attachment (id=15424) [details]
soapbox-0.3.1.ebuild

Why does this remind me of the "sandbox" portage feature? :-)

That's what led me to soapbox in the first place...  I wanted a standalone
program to track where a commercial installer wrote files, and happened to find
this.

BTW, this does not appear to build cleanly on sparc, I will investigate.

ryan, what's news on the sparc front then?

Erm, sorry for the delay...  I'll have to reassemble my ultra1 to get the patch
needed to run this on sparc.

I still don't have access to a sparc machine with gentoo, but I am currently
enlisting the help of #gentoo-sparc at the moment...

By the way, amd64 works fine as well.

Builds fine for me.

Sparc at least needs a DEPEND of >=sys-libs/glibc-2.3.2-r3

Created an attachment (id=22733) [details]
soapbox-0.3.1.ebuild

Added amd64/sparc keywords and dependency

Whilst we're at it... You can take out src_unpack() and src_compile(), no need
for either of those. Also add in IUSE="" (I believe that this is required under
current policy, although the docs may not reflect this...). You should also
~ify the keywords (except amd64) as new ebuilds shouldn't be added as stable.

Ping.  Ebuild has been tested with x86/amd64/sparc platforms, as specified in
previous comments.

Still waiting for you to fix the QA problems on this before we can think about
adding it...

Sorry, this package has kinda slipped off my radar...  I will see about
converting the ebuild soon

Created an attachment (id=49349) [details]
soapbox-0.3.1.ebuild

all outstanding ebuild issues fixed

cleaned up and added to portage