As some of you know, I keep my own overlay (on Github) which is mostly compatible with both Gentoo and Funtoo, but where the differences exist I favor Funtoo. In any case, there are two things I'd like some community help with.
First, I began doing all of my overlay work on my desktop computer. However, lately I have been doing a lot of ebuild writing on my laptop. This is in many ways easier because my laptop is much faster than my desktop, so I can test ebuilds much more quickly with shorter dependency calculations and compile times. However, perhaps because I only know the most basic usage of git, it can be a bit tedious writing ebuilds on my laptop, transferring them to my desktop, then adding them to the overlay. Does anyone have any suggestions on how to make it easier when using two different computers?
The other question is more general. How can I essentially have a high QA standard for my overlay? I have a couple of ebuilds I have contributed to Flora, but I generally don't contribute to Flora until I feel like the ebuild is "mature" enough, and besides that it seems like additional tedium to keep new versions of ebuilds synced on both my personal overlay and Flora.
So if anyone has any good advice for either of these issues, I'd sure appreciate it, and perhaps there are others who could benefit from it as well.
1) I think the easiest way (if you'd like to hear that or not) is to get more comfortable with Git. To achieve what you desire, the very basics of Git are enough to reach your goal. Since I had these kind of irritations with Git also a lot (I'm developing on multiple different machines, too) and often forget the steps to do so, I'll start a little Cookbook-like guide to Git especially with a focus of geting a benefit of that scenario; I guess it will take me a week after the new year has started to figure out a few scenarios on my own and I'll post the Guide's URL here afterwards. But the short answer is: Git can help you doing everything you're searching for.
2) QA is a little bit in the eye of the beholder, everytime and relates on who you ask. I think that you package is mature enough when it works for you, reproduceable and not on a "9 out of 10 tries" - basis. If you commit to flora (or any repo else) and it contains errors, it is far more important someone who faces the errors can contact you and that you respond in a reasonable timeframe. So, I think it is very important that your Metadata file contains a valid eMail address of yourself and this should be an address, you are checking on a reasonable basis.
So, if your package produces problems in the wild, noone will shoot you, as long as you support what you delivered
This is the first important QA step in my eyes, the other one is: Testing before sending a pull request. And that's all in my eyes one should take care of!
I appreciate that. After a few days from your reply, I tried just using git from my laptop. It wasn't hard at all, although I still have plenty to learn.
Since I started my overlay over a year ago, I've only been sent emails twice regarding issues with ebuilds, and I fixed them within a couple of days. I try to be on the ball.
One thing I'd like to do but don't know how (and I couldn't find any info on how to do it) is to add a news entry on my overlay maybe once a month just letting people know what's new on the overlay (using 'eselect news read'). I tried creating a news entry once, but as far as I know it never created an alert saying there was news, so I must have done something incorrectly.
Good idea, good question but no idea myself. I look forward to the suggestion one hopefully will give