Summary: | xmlindent-0.2.17 (new ebuild) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sascha Herrmann <starfox899> |
Component: | New packages | Assignee: | Tom Martin (RETIRED) <slarti> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | gentoo, slarti |
Priority: | High | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://xmlindent.sourceforge.net/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | ebuild for xmlindent-0.2.17 |
Description
Sascha Herrmann
2005-11-25 00:27:51 UTC
Created attachment 73551 [details]
ebuild for xmlindent-0.2.17
Does xmlindent do anything GNU indent doesn't? As i wrote before xmlindent indents XML Files while GNU indent "only" reformats C/C++ code files! So as you can imagine both programs do completly different work (only using the same ideas)! Cool. I wasn't sure :) I'll try to add it to the try sometime this week. Sorry, I forgot to close this. Just curious. Why did you remove the ~x86 keyword Sascha proposed, and used ~amd64 ~sparc instead? He obviously tested his ebuild, so I see no reason why it should not go into x86 testing. (In reply to comment #6) > Just curious. Why did you remove the ~x86 keyword Sascha proposed, and used > ~amd64 ~sparc instead? He obviously tested his ebuild, so I see no reason why > it should not go into x86 testing. > Gentoo policy is not to mark on any archs that you, the committer, can't test on. I can't test on x86 (and I haven't had the chance to set up a 32 bit chroot on my amd64), so I can't keyword. If you'd like this keyworded x86, please file a bug assigned to x86@gentoo.org. Thanks :) |