Opened 18 years ago
Closed 18 years ago
#1818 closed defect (fixed)
MesaLib Nitpick
| Reported by: | Randy McMurchy | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | BOOK | Version: | |
| Severity: | minor | Keywords: | |
| Cc: |
Description
1) As with the libdrm and xterm instructions, can we go ahead and specify an installation prefix, then perhaps explain in the command explanation section why you may need to modify it? I just can't help but think that in the long run it would be best to specify *something* as the prefix and go with it. Doesn't matter what it is, just that it looks like we are recommending *something*.
2) The explanation about the demo programs says they are used to test DRI functionality. Actually, however, these programs work fine and can be good testing tools if you don't have DRI implemented. Seems they are more general programs used to test the GLX extensions.
Change History (2)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
All issues resolved as suggested. Thanks Randy.
Note:
See TracTickets
for help on using tickets.
I forgot to list another item in the MesaLib instructions. There are install commands that have '-o root' parameters. These are totally unnecessary and redundant as only root can use the -o parameter on the install command and then if root is issuing the command, the owner will *always* be root.
So, bottom line is that we are not giving a good "learning experience" by using commands improperly.