Hi, attached please find a new ebuild for innotop, a MySQL and InnoDB monitoring tool. I'm new to writing ebuilds, so please bear with me if it's not quite what you are looking for. innotop parses the results of MySQL's SHOW INNODB STATUS command in a way humans can understand. It is like mytop or mtop, except has a ton of features they don't have. I have reports of it working fine on many different operating systems.
Created attachment 96993 [details] dev-db/innotop-0.1.149.ebuild
I just thought of something, maybe my versioning strategy is not very smart. I have been incrementing the version every time I do a CVS commit. If I keep doing that, and create new ebuilds every time, I will barrage portage with a million changes. Any suggestions are welcome. I am not very familiar with how people usually do this type of thing. I'm thinking it is better for me to keep innotop's versioning divorced from CVS's revision number.
In the tree now, changed KEYWORDS from stable to unstable due to our policy. ebuild from http://www.xaprb.com/innotop/src/innotop-0.1.154.ebuild thanks for the report and for the job. Francesco P.S. Luckily sometimes I lurk planetmysql.org ;)
Thank you! I had despaired of anything happening, and opened a bug report at breakmygentoo, https://bugs.breakmygentoo.net/view.php?id=257. Two things: 1) should I ask them to cancel adding it to their overlay? 2) in that bug report, they brought up some issues with the package itself not containing some needed files, COPYING and LICENSE. I'll add those files to the package pronto.
Actually I'm not sure about the COPYING and LICENSE files -- please advise if I need to add them. I've been reading through the Gentoo docs again and it looks like I don't need them.
c#4 1) Ping them that it has been added to gentoo tree would suffice, it's their choice then to add it or not to their overlay. 2) see below c#5 I'm not an expert in lawyer stuff but since you are upstream and you have put a LICENSE="|| ( Artistic GPL-2 )" variable inside the ebuild my thoughts are that it suffice. Looking at the innotop.html file however the licence look more like the "as-is" as described in $(portageq portdir)/licenses/as-is . That's your choice :)
A LICENSE or COPYING file normally contains a copy of the license under which the package (and all it program code, graphics, sounds etc) was released. As the current package file of innotop doesn't contain any license information we can't be sure about the restrictions resulting from using the software. In my opinion, software without clear license information shouldn't be added to Gentoo's portage tree. So if you are the maintainer of this piece of software simply add a file "COPYING" to the package which contains the license information (e.g. a copy of GPL-2).
OK, I have added a LICENSE file to the 0.1.160 package (and updated the ebuild to match what's in the portage tree, so you don't have to fuss with it). I'm happy with either GPL2 or Artistic, which is expressed in the source code itself, so I put GLP2 in LICENSE. 0.1.160 really only adds Windows compatibility. I notice there is no ~win32 architecture ;-) I'm afraid to modify the 0.1.154 .tar.gz file because then it'll fail checksums. If that's an unfounded fear, let me know. At some point I plan to add a bunch of significant new features based on ideas I got at the recent MySQL Camp un-conference. Then I'll submit an update to this bug, if that's OK.
(In reply to comment #8) > OK, I have added a LICENSE file to the 0.1.160 package (and updated the ebuild > to match what's in the portage tree, so you don't have to fuss with it). I'm > happy with either GPL2 or Artistic, which is expressed in the source code > itself, so I put GLP2 in LICENSE. hem ... I can't see it, maybe the tar.gz is created by a Makefile that need to be updated ? > I'm afraid to modify the 0.1.154 .tar.gz file because then it'll fail > checksums. If that's an unfounded fear, let me know. Yes please, change packages once they are on mirrors is a mayor pain for an undefined amount of time there are part of the mirrors with the wrong one, the user need then to manually delete it from $DISTFILES etc.etc. > At some point I plan to add a bunch of significant new features based on ideas > I got at the recent MySQL Camp un-conference. Then I'll submit an update to > this bug, if that's OK. Sure, for the moment the ebuild has been upgraded to 0.1.160 with the windows changes.
You're right, I forgot to add the LICENSE file to the .tar.gz. I fixed my build script now, but I'll refrain from adding that file till a future release, so as not to break checksums.
Created attachment 107337 [details] dev-db/innotop-1.0.1.ebuild, for stable version 1.0.1 innotop is now at version 1.0.1 and I consider it stable. (I don't know what process gentoo goes through for stable though). This release is actually a very minor fix or two over the previous, but I would like to get this version into the tree for possible stable status while I work towards 1.4. Note I am hosting innotop on sourceforge.net now. Please check the ebuild for me -- I'm not sure I got it all correct for the sourceforge download URL.
1.4.0 is about ready to release, and I'd like to get it into the portage tree. Is there anything I can do to help this process? Is "maintainer wanted" out of my hands, or can I be the maintainer, or help somehow?
(In reply to comment #12) > 1.4.0 is about ready to release, and I'd like to get it into the portage tree. it is, committed now. > > Is there anything I can do to help this process? Is "maintainer wanted" out of > my hands, or can I be the maintainer, or help somehow? You can become a gentoo developer, we cannot allow cvs access to the users, at the moment mysql-team is seriously understaffed and we need experienced mysql devs.
