BerylonEdgy guide

[Matthew East]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

* Travis Watkins:
> On 10/21/06, Joseph Price <pricechild at gmail.com> wrote:
>> For the binary nvidia .run:
>> The use KNOWS what he is installing, wheras with the packages you have to
>> trust the unsigned packages to be non-harmful and built well.
>> In the event of the kernel upgrade, the user can simply re-run the file to
>> recompile the module, wheras those using amaranth's packages may have to
>> wait a while for him to rebuild.
> 
> The binary .run also seems to end up broken when mesa is upgraded but
> doesn't make it obvious why it broke.

It looks to me as if there are pros and cons to each approach. As a
result, if you document those, the user can make an informed choice
between them.

But, Eric is right - please integrate any information with the existing
pages about Beryl!

Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFPGxQtSaF0w5rBv8RArSUAJ9Nxi+po2EuwRhd74n3IodOmrk9lACfeGFo
mo69WoPrffRKH2xt0uTmKgc=
=7zj2
-----END PGP SIGNATURE-----