View previous topic :: View next topic |
Author |
Message |
PhiJ Apprentice
Joined: 20 Dec 2005 Posts: 173 Location: UK
|
Posted: Sun Sep 07, 2008 1:36 pm Post subject: Testing Ebuilds |
|
|
Stupid question I know, but I can't find the answer (which is probably obvious somewhere). Chuck is masked by a missing keyword. To test it on my arch, what do I do? Do I just have to see if it works, and then post that is does work (or doesn't and what errors I get) on bugzilla? Or do I have to do more than that. Also, what will I need to say about my system on the bug report? |
|
Back to top |
|
|
Polynomial-C Retired Dev
Joined: 01 Jun 2003 Posts: 1432 Location: Germany
|
Posted: Sun Sep 07, 2008 1:47 pm Post subject: |
|
|
Hi,
install the package from portage, give it some thoroughly testing and if it works with no big glitches (like data corruption or frequent crashes) file a keyword request for the package at https://bugs.gentoo.org
Cheers
Poly-C _________________ The manual said "Requires Windows10 or better" so I installed GNU/Linux...
my portage overlay
Need a stage1 tarball? (Unofficial builds) |
|
Back to top |
|
|
myceliv Apprentice
Joined: 29 Nov 2007 Posts: 178
|
Posted: Sun Sep 07, 2008 11:03 pm Post subject: |
|
|
There are also these guidelines and test system setup requirements for amd64 arch testers, that are probably pretty up to date, and give a little more detail. But since you're not an official tester, not sure how critical that would be. You could email one of the arch tester leads or ask on irc. |
|
Back to top |
|
|
|