Bugzilla Bug 57671

Ebuild for Mattricks 0.6

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Created an attachment (id=35787) [edit]
Mattricks 0.6 ebuild

this  dev-python/pyxml should be added to the depencies too, otherwise it wont
work.

Always use the full category/packagename in the DEPEND variables.

Please tidy up in the ebuild a bit and resubmit.  Reopen with a new ebuild.

Feel like cleaning this ebuild up a bit?

Doing that... :D Sorry for the delay... Busy vacations... ;)

Check bug 61615

*** Bug 61615 has been marked as a duplicate of this bug. ***

Created an attachment (id=38155) [edit]
New fixed ebuild...

Here it is... You told me to reopen with a new ebuild and I though it was to
submit a new bug... now I got it... it was just to reopen THIS bug! LOL, it
really didn't make sense. I'm sorry!

What's the convention on capital letters ebuilds?
I'd prefer it to be all small letters..

The standard for ebuild names is all lowercase. 
http://www.gentoo.org/doc/en/policy.xml for more information.

Added to CVS

Hi, I think this bug should be reopened. For some reason the version in CVS
doesn't seem to work. There's a problem about executing setup.py. However, that
doesn't happen in my version. Their diff is as follows:

euler ~ # diff /usr/local/portage/games-misc/Mattricks/Mattricks-0.6.ebuild
/usr/portage/games-util
/mattricks/mattricks-0.6.ebuild  
3c3
< # $Header: $
---
> # $Header: /var/cvsroot/gentoo-x86/games-util/mattricks/mattricks-0.6.ebuild,v 1.1 2004/09/01 14:05:31 wolf31o2 Exp $
4a5
> MY_P=${P/m/M}
7c8
< SRC_URI=http://www.lysator.liu.se/mattricks/files/${P}.tar.gz
---
> SRC_URI="http://www.lysator.liu.se/mattricks/files/${MY_P}.tar.gz"
9c10
< LICENSE="GPL"
---
> LICENSE="GPL-2"

I'm just curious, but looking at that diff, the only things changed are the
downloaded file has the m in mattricks replaced with an M so it downloads the
correct file, and the license is set to the proper one.

The files downloaded and installed are exactly the same.

What isn't working?

...and better yet, you should file a bug on what isn't working so it can be
tracked as an actual bug and not an enhancement bug (like this one was).  Be
sure to include all the normal bug infomation.

Thanks

Added bug 63032.