Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Drop ppc64 keywords as it does not even compile | Markus Rothe | 2006-12-10 | 1 | -2/+2 |
| | | | | (Portage version: 2.1.1-r2) | ||||
* | Added automake dep wrt Bug #151564. | Thomas Cort | 2006-10-16 | 1 | -1/+9 |
| | | | | (Portage version: 2.1.1-r1) | ||||
* | Ported all ebuilds to modular X for Bug #126934. | Thomas Cort | 2006-07-22 | 1 | -3/+6 |
| | | | | (Portage version: 2.1-r1) | ||||
* | With respect to the keywording policy, this shouldn't be keyworded for alpha | Fernando J. Pereda | 2005-08-05 | 1 | -2/+2 |
| | | | | (Portage version: 2.0.51.22-r2) | ||||
* | We seem to have yet another unfortunate incident of | Ilya Volynets | 2005-06-28 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | keyword-happy developer. There have been numerous instances of untested unapproved packages being keyworded, this was discussed time and again, the issue is mentioned in developer documentation, added to developer quiz, and voila, we have it again.. This time multiple packages in dev-dotnet/ category were marked as mips, ~mips, sparc, ~sparc, as well as working on other arches. It was confirmed that dotnet doesn't even build on most of these, yet they were keyworded. Oh well... There seems to be no way to teach some people. Removing mips and sparc keywords (Manifest recommit) (Portage version: 2.0.51.19) | ||||
* | Version bump. | Michael Tindal | 2005-06-21 | 1 | -0/+47 |
(Portage version: 2.0.51.22-r1) |