| 1 |
On 09/10/03 Brian Friday wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> Holy never finished the thought batman! Teaches me to spell |
| 5 |
> check before I finish... |
| 6 |
> |
| 7 |
> --- |
| 8 |
> Of course this only works in situations where a block has |
| 9 |
> been identified by developers but perhaps (again thinking |
| 10 |
> way ahead) doing a scan after the package has been imaged |
| 11 |
> (ie /var/tmp/portage/pkgname/image) but before it is |
| 12 |
> merged. This scan would check to make sure we won't be |
| 13 |
> overwriting an application/file with this new ebuild that |
| 14 |
> isn't an upgrade or downgrade of the package being built. |
| 15 |
|
| 16 |
That's exactly what I'm currently working on, I hope once it is finished |
| 17 |
and integrated into portage it will reduce the number of |
| 18 |
file collision bugs to near zero. |
| 19 |
Also I don't think you mean SLOTs but virtual dependencies like |
| 20 |
virtual/mta as SLOTs are package-internal. |
| 21 |
For the editor problem I think we can just install a simple wrapper |
| 22 |
script that calls $EDITOR, it has the advantage that the default editor |
| 23 |
can be changed in one place and needs no change for things that can use |
| 24 |
$EDITOR directly. |
| 25 |
|
| 26 |
Marius |
| 27 |
|
| 28 |
-- |
| 29 |
Public Key at http://www.genone.de/info/gpg-key.pub |
| 30 |
|
| 31 |
In the beginning, there was nothing. And God said, 'Let there be |
| 32 |
Light.' And there was still nothing, but you could see a bit better. |
Archives