SystemTapGui rpms/specfile for fedora.

[anithra]

William Cohen wrote:
> anithra wrote:
>   
>> Hi Will,
>>
>> Ive uploaded the RPM,SRPM and spec file for SystemTapGui-1.0-1 on
>> sourceforge. This is the plugin version. The SystemtapGui client has
>> been built as per the  guidelines in
>> https://fedoraproject.org/wiki/Packaging/EclipsePlugins.
>> The packages have been verified with rpmlint. I have included the
>> SystemTapGuiServer binary rpm for x86 only. Please let me know if you
>> require the binary for other platforms also and if anything else is
>> missing.
>>
>> https://sourceforge.net/project/showfiles.php?group_id=169234&package_id=306913
>>
>>
>> Thanks,
>> Regards,
>> Anithra.
>>     
>
> Hi Anithra,
>
> I was able to build this no problem the eclipse-SystemTapGui-1.0-1.fc10.src.rpm
> locally on my x86_64 F10 machine once the BuildRequires were installed on the
> machine.
>
> The SystemTapGuiServer-1.0-1.src.rpm should be buildable on i386, x86_64, ppc,
> and ppc64 (the primary architectures). There are rawhide repositories for the
> those primary architectures at:
>
> http://download.fedora.redhat.com/pub/fedora/linux/development/
>
> There are rpms for eclipse for those architectures in the subdirectories. Unless
> there are if defs for specific architectures. I would be suprised if there was
> anthing intrinsic in this code to prevent it from building
>   
> http://fedoraproject.org/wiki/Packaging/Guidelines#Architecture_Support
>
> Some comments about tar ball and build:
>
> Shouldn't the SystemTapGuiServer.spec file correct have the correct information
> for point to the sourceforge page?
>
> The make file should use $(CXX) instead of $(CC), should also be able to get rid
> of the -lstdc++ in LDFLAGS.
>
> Build ./test/testdriver.o, do not include it in the tar file.
> Shouldn't have cscope.out in the tarball.
>
>
> The procedure for getting packages into fedora is at:
>       http://fedoraproject.org/wiki/PackageMaintainers/Join
>
> -Will
>
>   
Hi Will,

Thanks for looking at it.  I think i didn't do a very good job of 
explaining the SystemTapGui architecture in our weekly call so here goes:

The  SystemTapGuiServer-1.0-1.src.rpm is c++ code and should be 
buildable on any architecture. It does not have any eclipse code. This 
is a basic server daemon that recieves requests to execute scripts from 
the GUI client. it executes the scripts, collects all output to stderr 
and stdout from the process and funnels it via a socket to the client. 
Since it is C++ code the binaries are architecture-dependent.

The eclipse-SystemTapGui-1.0-1.fc10.src.rpm package (client) constitutes 
eclipse plugins. It is java code and the binary is architecture 
independent. This package provides the IDE and the visualization 
interface. It has eclipse 3.4 as a prereq and since we have not been 
able to find eclipse 3.4 installables for a few architectures(s390, 
ppc64) it might not be possible to install the GUI client on all 
architectures. Since this is a client-server application we figured this 
should not be a problem as the users only need to install the server on 
the system on which they wish to run the scripts, we can have the server 
on a s390 machine and the eclipse-based client on an x86 system.

Thanks for the review comments, I have made changes to the spec file, 
makefile as per your comments and uploaded it to sourceforge.  I have 
raised a review request for the eclipse-SystemTapGui-1.0-1.fc10.src.rpm 
package as per the guidelines in 
http://fedoraproject.org/wiki/PackageMaintainers/Join. I need to find a 
sponsor as this is my first package. Any suggestions on how to go about 
that?.

https://bugzilla.redhat.com/show_bug.cgi?id=483205

Regards,
Anithra.
>
>
>
> -Will
>