[opensuse-buildservice] Proposal: Add LSB Symbol generation to the openSUSE build system.
Hello Build Team, I have a proposal. I am working with the LSB (and ISP RAS) on a project to improve their symbol data in their database for ISV applications. If you look at their project ( http://ispras.linux-foundation.org/index.php/Main_Page ), you will see they have an LSB Application Test Kit (ATK). An application writer can have symbol data from their application submitted to the LSB Infrastructure Project DB. Currently, they have PERL scripts that use utilities like 'readelf' to extract the symbol information. They also have a web front end to make it easy to submit the data. The goal is that with symbol data from a broad set of applications, that better decisions can be made about what APIs are being used (and can be standardized) by the LSB. The LSB (and Markus Rex) would like us to run these scripts to get the symbol data to add to the LSB database. It seems to me that it would be easier (and quicker) to add the scripts to the openSUSE build system. I would envision a check box that could be selected from the openSUSE build interface that would say "Generate LSB Symbol data files", to make it optional if people would like. Then, as part of the build, the symbol files would be generated and available for the LSB (ISP RAS) engineers to grab and put into the database. Thoughts? Thanks for your time, Darren --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Darren, sorry for the late answer. On Friday 31 August 2007 18:17:30 wrote Darren Davis:
Hello Build Team,
I have a proposal. I am working with the LSB (and ISP RAS) on a project to improve their symbol data in their database for ISV applications. If you look at their project ( http://ispras.linux-foundation.org/index.php/Main_Page ), you will see they have an LSB Application Test Kit (ATK). An application writer can have symbol data from their application submitted to the LSB Infrastructure Project DB. Currently, they have PERL scripts that use utilities like 'readelf' to extract the symbol information. They also have a web front end to make it easy to submit the data. The goal is that with symbol data from a broad set of applications, that better decisions can be made about what APIs are being used (and can be standardized) by the LSB.
The LSB (and Markus Rex) would like us to run these scripts to get the symbol data to add to the LSB database. It seems to me that it would be easier (and quicker) to add the scripts to the openSUSE build system. I would envision a check box that could be selected from the openSUSE build interface that would say "Generate LSB Symbol data files", to make it optional if people would like. Then, as part of the build, the symbol files would be generated and available for the LSB (ISP RAS) engineers to grab and put into the database.
As a first step, I would like to suggest to create a project for this and provide a package there what provides the test suite. Additionally you can create another package which reuses this package and does BuildRequire all packages you would like to test. So the service would run it for all files/applications you do define automatically each time they do change. Later on we can integrate it into our rpmlint check, which we want to run by default on each packge. And even later we can offer this as a QA service, when we have a real QA infrastructure, but this a bit more fare away. Does this makes sense to you ? We can help you to get started with the OBS, feel free to contact us directly via irc or IM or .... thanks adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter wrote:
Hi Darren,
sorry for the late answer.
On Friday 31 August 2007 18:17:30 wrote Darren Davis:
Hello Build Team,
I have a proposal. I am working with the LSB (and ISP RAS) on a project to improve their symbol data in their database for ISV applications. If you look at their project ( http://ispras.linux-foundation.org/index.php/Main_Page ), you will see they have an LSB Application Test Kit (ATK). An application writer can have symbol data from their application submitted to the LSB Infrastructure Project DB. Currently, they have PERL scripts that use utilities like 'readelf' to extract the symbol information. They also have a web front end to make it easy to submit the data. The goal is that with symbol data from a broad set of applications, that better decisions can be made about what APIs are being used (and can be standardized) by the LSB.
The LSB (and Markus Rex) would like us to run these scripts to get the symbol data to add to the LSB database. It seems to me that it would be easier (and quicker) to add the scripts to the openSUSE build system. I would envision a check box that could be selected from the openSUSE build interface that would say "Generate LSB Symbol data files", to make it optional if people would like. Then, as part of the build, the symbol files would be generated and available for the LSB (ISP RAS) engineers to grab and put into the database.
As a first step, I would like to suggest to create a project for this and provide a package there what provides the test suite.
Additionally you can create another package which reuses this package and does BuildRequire all packages you would like to test. So the service would run it for all files/applications you do define automatically each time they do change.
Later on we can integrate it into our rpmlint check, which we want to run by default on each packge.
And even later we can offer this as a QA service, when we have a real QA infrastructure, but this a bit more fare away.
Does this makes sense to you ?
We can help you to get started with the OBS, feel free to contact us directly via irc or IM or ....
thanks adrian
Yes, this does make sense so I will give this a try as my first step. I will also get Alexey to setup an account on the build service. Thanks, Darren --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Donnerstag, 6. September 2007 17:44 schrieb Darren Davis: Hi Darren, I have a few questions.
The LSB (and Markus Rex) would like us to run these scripts to get the symbol data to add to the LSB database. It seems to me that it would be easier (and quicker) to add the scripts to the openSUSE build system. Is it interesting for all kind of packages or just special ones? What is happening with the generated data later? Would you like to see the LSB database integrated in the buildserver later on or are these kind of data just for download and import into the other system? How are different architectures handled?
Thanks, Klaas
-- Klaas Freitag Architect OPS/IPD SUSE LINUX Products GmbH - Nuernberg --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Klaas Freitag wrote:
Am Donnerstag, 6. September 2007 17:44 schrieb Darren Davis:
Hi Darren,
I have a few questions.
The LSB (and Markus Rex) would like us to run these scripts to get the symbol data to add to the LSB database. It seems to me that it would be easier (and quicker) to add the scripts to the openSUSE build system.
Is it interesting for all kind of packages or just special ones?
I think that the LSB is looking for a broad application mix (See Alexey's reply). Basically the LSB wants to know what interfaces are being used by applications being built today.
What is happening with the generated data later? Would you like to
The data is put into the LSB Infrastructure Database and can be used by the LSB to determine what interfaces are the most important. To get and idea, check out; http://www.linux-foundation.org/navigator/browse/app.php
see the LSB database integrated in the buildserver later on or are these kind of data just for download and import into the other system?
I guess they are primarily put into the LSB database on their website and use it for decision making purposes as it relates to future interfaces in the LSB standard, but the data can prove useful for an application developer. The developer gets information like if the interfaces they are using are in the LSB or not. In the end, just symbol data for the application.
How are different architectures handled?
Currently the have separate data for IA32 and x86-64. They do want to add all the supported LSB architectures, but they don't have all that data at this point. This is probably a question for Alexey at ISP RAS, but I am pretty sure they want all architectures in the future.
Thanks,
Klaas
I will work with Alexey to see if we can get the LSB scripts into the OBS as Adrian instructed. I am currently attending the SUSE Labs conference, so I won't get started on that for a week or so. Thanks for your time, Darren --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter wrote:
Hi Darren,
sorry for the late answer.
On Friday 31 August 2007 18:17:30 wrote Darren Davis:
Hello Build Team,
I have a proposal. I am working with the LSB (and ISP RAS) on a project to improve their symbol data in their database for ISV applications. If you look at their project ( http://ispras.linux-foundation.org/index.php/Main_Page ), you will see they have an LSB Application Test Kit (ATK). An application writer can have symbol data from their application submitted to the LSB Infrastructure Project DB. Currently, they have PERL scripts that use utilities like 'readelf' to extract the symbol information. They also have a web front end to make it easy to submit the data. The goal is that with symbol data from a broad set of applications, that better decisions can be made about what APIs are being used (and can be standardized) by the LSB.
The LSB (and Markus Rex) would like us to run these scripts to get the symbol data to add to the LSB database. It seems to me that it would be easier (and quicker) to add the scripts to the openSUSE build system. I would envision a check box that could be selected from the openSUSE build interface that would say "Generate LSB Symbol data files", to make it optional if people would like. Then, as part of the build, the symbol files would be generated and available for the LSB (ISP RAS) engineers to grab and put into the database.
As a first step, I would like to suggest to create a project for this and provide a package there what provides the test suite.
Alexey has now done this. http://build.opensuse.org/project/show?project=home%3Akhoroshilov though it probably should be put under LSB with Jiri's tools.
Additionally you can create another package which reuses this package and does BuildRequire all packages you would like to test. So the service would run it for all files/applications you do define automatically each time they do change.
A little fuzzy on this step. Can you point me to an existing example?
Later on we can integrate it into our rpmlint check, which we want to run by default on each packge.
And even later we can offer this as a QA service, when we have a real QA infrastructure, but this a bit more fare away.
Does this makes sense to you ?
We can help you to get started with the OBS, feel free to contact us directly via irc or IM or ....
thanks adrian
Thanks again, Darren --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Adrian Schröter -
Darren Davis -
Klaas Freitag