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