On Friday 11 January 2008, Bernd Steinhauser wrote: > this is sth. reading your e-mail drove me nuts as i cant figure out what "sth" means. google says "Sonic The Hedgehog". not sure how this applies to Gentoo (he's really fast?).
> that has been brought up in the KDE4 forums thread and on
> irc. The thing is, that if you're using a live ebuild you might very
> likely run into bugs, that have been introduced in a newer revision.
> Now when you get in touch with upstream about that bug it might be very
> useful if you can tell them, that you know, that a specific version in
> the past worked. The idea was now to add the ability to the scm eclasses
> to do this automatically.
when i'm upstream, i leverage `svn info` and such so that the active rev makes
it into the version information. but this would of course require changes to
upstream stuff.
> So after installation then sth. like this
> ${CAT}/${P} merged at revision (or commit) ${REVISION}
> to a file like /var/log/portage/scm.log.
> Now I'm sure there are a few dirty ways to achieve this, but I wonder if
> there is an easy and clean way to do this?
>
> The problem is (I think so), that you can't just write sth. to / because
> of the sandbox, so there needs to be a way to get around that, and it
> should also happen after installation (post_inst).
considering you care about the *src* and not *pkg*, you'd probably want to
have it done in src_install. if you exported a variable, it'd be retrievable
later in the vdb, but that isnt easy for users.
installing into a common accepted directory (like /usr/share/scm/$P) is one
possibility, but that too kind of sucks. but it would be trivial for users
to glean ...
-mike
signature.asc
Description: This is a digitally signed message part.
