| 1 |
On Mon, 2013-04-22 at 14:11 +0700, A.G.Grozin@×××××××.su wrote: |
| 2 |
> On Sun, 21 Apr 2013, Stelian Ionescu wrote: |
| 3 |
> > On Sun, 2013-04-21 at 09:49 +0700, A.G.Grozin@×××××××.su wrote: |
| 4 |
> >> On Sat, 20 Apr 2013, Stelian Ionescu wrote: |
| 5 |
> >>> clozurecl-1.9-r3 is not a live ebuild, what makes you think that ? |
| 6 |
> >> src_prepare() { |
| 7 |
> >> svn upgrade >/dev/null || die |
| 8 |
> >> cp /usr/share/common-lisp/source/asdf/build/asdf.lisp tools/ || die |
| 9 |
> >> } |
| 10 |
> >> This is not acceptable in the main tree. |
| 11 |
> > Why not ? |
| 12 |
> > |
| 13 |
> >>> Please don't put snapshots in portage unless really necessary, and this |
| 14 |
> >>> is not the case since upstream makes regular releases. |
| 15 |
> >> So why 1.9-r3 gave something unpredictable which varies with time? |
| 16 |
> > What varies ? |
| 17 |
> The result of |
| 18 |
> svn upgrade |
| 19 |
> of course! It upgrades the source directory to the current |
| 20 |
> (time-dependent) state of the upstream svn. So, this is a live ebuild. |
| 21 |
|
| 22 |
That command upgrades the metadata format to the most recent because |
| 23 |
upstream uses a very old version of subversion. |
| 24 |
|
| 25 |
> Also, it requires an internet connection at the emerge time. |
| 26 |
|
| 27 |
No it doesn't. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Stelian Ionescu a.k.a. fe[nl]ix |
| 32 |
Quidquid latine dictum sit, altum videtur. |
| 33 |
http://common-lisp.net/project/iolib |
Archives