[csw-maintainers] freshening up Ganglia packages/need rrdtool
Dagobert Michelsen
dam at opencsw.org
Thu Nov 24 21:53:06 CET 2011
Hi Daniel,
Am 24.11.2011 um 19:06 schrieb Daniel Pocock:
>>> I suggest rebuilding this also to the latest naming standard which would be
>>> libconfuse0 and CSWlibconfuse0 together with CSWlibconfuse-dev and libconfuse_dev
>>> and obsolete the old name. You can look at
>>> http://sourceforge.net/apps/trac/gar/browser/csw/mgar/pkg/libssh2/trunk/Makefile
>>> for an example. Please let me know if I can assist you in this matter.
>>>
>>>
>> The example is not so clear, because libssh2 is downloading
>> libssh2-1.3.0.tar.gz, while there is no libconfuse0-2.7.0.tar.gz to download
>>
>> Therefore, where do I use the real name, and in which variables do I use
>> libconfuse0 with the 0?
>
> I played around with it a bit and ended up with these:
>
> The following packages have been built:
>
> CSWlibconfuse0-1
> /home/daniel/pkgs/libconfuse0_1-2.7,REV=2011.11.24-SunOS5.10-sparc-CSW.pkg.gz
> CSWlibconfuse0-dev
> /home/daniel/pkgs/libconfuse0_dev-2.7,REV=2011.11.24-SunOS5.10-sparc-CSW.pkg.gz
>
> Can you please check my Makefile and see if I'm doing it correctly?
Done on devel@
> What is the next step to release? Would you be able to release them for
> me (I'm 7 hours ahead of you now) so I can test in the morning?
You need to csw-upload-pkg and wait until they hit unstable/, then you mail to
buildfarm@ to install these.
>>> After that I suggest you release libconfuse so I can install it and then proceed with ganglia.
>>> Is this possible?
>>
>> Can you elaborate on `release'? I notice that /home/testing doesn't
>> exist any more - what is the preferred way to release?
The packages which you drop in /home/experimental/<mydir> will appear in
buildfarm.opencsw.org/experimental.html#<mydir>
for manual installation.
Best regards
-- Dago
--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896
More information about the maintainers
mailing list