We built our first package nearly 19 years ago. We were able to fork and compile another 3 packages in the space for 4 more years, which is going pretty well from what I have heard. <br><br>So far they are all operating as expected, the level of sysadmin work to maintain them hasn't been too bad. The two packages with "-xx" architecture have been the least trouble.I don't believe I have quite got to the stage of wanting to send a SIGTERM to the "-xy" packages, but sometimes they push you. They all occasionally send unexpected SIGs back to us. most of which we have had to develop handlers for, so things are pretty well in control. The oldest "-xx" package is undergoing certification testing next year, so that is likely to be a challenge.<br>
<br>Our first package, an "-xy", is very much in the open-source mould, and is adding lots of language bindings. In fact I think it is getting pretty close on improving on my own source code, so I am pretty happy with that.<br>
<br>One thing is for sure though, is that the operating cost of running packages is always on the increase - the vendors keep on pushing new hardware platforms. At least one isn't all that happy with the music input interface I bought last year, and I think would have rather I got the latest one from Cupertino. Funny thing though, mainly due to my "-xx" package I compiled with, is that all have developed their own very good music output plugin capability which I am very happy with. The 3 oldest packages network regularly with other similar packages to produce a collaborative music output which they enjoy greatly. (Unfortunatetly the cost of providing and developing the music output plugins, as well the networking aspects thereof, seems to take most of our spare funds.)<br>
<br>One other annoyance is that 3 of our packages have had to have their food processing peripherals straightened. I am pretty sure that the technical specialist doing the work has at least two trips to Tahiti out of the fees he charged.<br>
<br>Anyway despite all this, I am looking forward to see what forks from our packages in the future.<br><br clear="all">Regards, Martin<br><br><a href="mailto:MartinVisser99@gmail.com">MartinVisser99@gmail.com</a><br>
<br><br><div class="gmail_quote">On Tue, Nov 25, 2008 at 2:03 PM, Steve Walsh <span dir="ltr"><<a href="mailto:steve@nerdvana.org.au">steve@nerdvana.org.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Paul Shirren wrote:<br>
> I need to file a launchpad bug because ours didn't arrive with a man<br>
> page. Did anyone get a man page with theirs?<br>
</div>We haven't even started thinking about compiling one, but I have heard<br>
from a lot of Developers that there is quite a bit of hard work to get<br>
the source package to even start to compile, often involving yelling,<br>
groaning, swearing and techniques from the pair-programming school of<br>
thought...<br>
<div class="Ih2E3d">> Trying to communicate with it is like fuzz testing. There must be a<br>
> source package somewhere to understand how this thing is supposed to<br>
> work.<br>
</div>Apparently this gets easier the more you build, but stay away from tools<br>
that do distributed compiling, that can get you in some legal hotwater.<br>
<div class="Ih2E3d">> Also the installation really could do with more automation of<br>
> housekeeping tasks. I have to manually clean up logs. Why isn't there<br>
> a cron script for this?<br>
</div>This is something we are definitely lagging behind in the closed source<br>
world on, but their solution just involves throwing money at addons to<br>
make the root cause go away...<br>
<font color="#888888"><br>
--<br>
--==--<br>
Steve Walsh<br>
RHCE<br>
Vice President / SysAdmin Team member- Linux Australia<br>
Networks and Technology - <a href="http://Linux.conf.au" target="_blank">Linux.conf.au</a> 2008<br>
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
<br>
_______________________________________________<br>
linux-aus mailing list<br>
<a href="mailto:linux-aus@lists.linux.org.au">linux-aus@lists.linux.org.au</a><br>
<a href="http://lists.linux.org.au/listinfo/linux-aus" target="_blank">http://lists.linux.org.au/listinfo/linux-aus</a><br>
</div></div></blockquote></div><br>