| 1 |
El dom, 14-04-2013 a las 12:08 +0200, Michał Górny escribió: |
| 2 |
> On Sun, 14 Apr 2013 11:59:14 +0200 |
| 3 |
> Pacho Ramos <pacho@g.o> wrote: |
| 4 |
> |
| 5 |
> > El dom, 14-04-2013 a las 11:45 +0200, Michał Górny escribió: |
| 6 |
> > > On Sun, 14 Apr 2013 11:40:03 +0200 |
| 7 |
> > > Pacho Ramos <pacho@g.o> wrote: |
| 8 |
> > > |
| 9 |
> > > > # >=mono-0.92 versions using mcs -pkg:foo-sharp require shared memory, so we set the |
| 10 |
> > > > # shared dir to ${T} so that ${T}/.wapi can be used during the install process. |
| 11 |
> > > > export MONO_SHARED_DIR="${T}" |
| 12 |
> > > |
| 13 |
> > > Don't use ${T} in global scope. And just don't export them |
| 14 |
> > > in the global scope either. |
| 15 |
> > |
| 16 |
> > Why not? |
| 17 |
> |
| 18 |
> Let's start with the fact that ${T} is only partially persistent |
| 19 |
> by the words of PMS. I don't know if it's really relevant here but |
| 20 |
> you're exporting persistent variables with value based on |
| 21 |
> an non-persistent one. |
| 22 |
> |
| 23 |
> Thinking about it more, it probably would work. As long as you don't |
| 24 |
> assume anything about those directories on pkg_*rm() where ${T} would |
| 25 |
> have changed already and your variables wouldn't. |
| 26 |
> |
| 27 |
|
| 28 |
Yes, they will be needed at compile time, that would explain why no |
| 29 |
problem raised for now :/ Thanks for the info |
| 30 |
|
| 31 |
> Also, why are you exporting HOME? PMS does that already... |
| 32 |
> |
| 33 |
|
| 34 |
Probably because it's inherited from current mono.eclass, but, are you |
| 35 |
sure PMS does that already? There are more examples in the tree (in |
| 36 |
eclasses and ebuilds) exporting HOME in similar way (vim.eclass for |
| 37 |
example) :/ Or maybe it was started to be exported more recently and |
| 38 |
this is only a relic :| |
Archives