Menu
▾
▴
net-snmp-coders
|
From: Need H. <snm...@ya...> - 2007-06-07 19:32:10
|
Ok, my company would like me to start discussing how to incorporate NetSNMP into the company's build environment. I explained the following stuff: - Indicated "./configure", "make" and "make install" were required for NetSNMP - Indicated "snmp.conf" and "snmpd.conf" files exist to define stuff - Indicated certain environment variables could be used if desired - Indicated other stuff as well.... as much as I came across so far.... :>P During this discussion, the "build-production" people at my company informed me we can not perform the "configure" command as part of our "build process". Instead it would be necessary to understand exactly what the "configure" command (and I guess the "make" and "make install" commands as well) do "behind the scenes" so our build process and perform these exact steps ourselves. I was told we do not want to execute a script file with all of the required commands and options in it as well. Anyway, is this a common approach to integrating NetSNMP into a business application (ie: not using the standard setup commands/options as part of the command line or in a script file)? It scares me not to use the standard steps to get NetSNMP configured/running. Perhaps someone can explain to me whether this is weird or not. If so, then perhaps you can give me a quick overview as to how NetSNMP should "normally" be integrated in a build system. I understand no one knows how our build system works (neither do I), but any input into this topic would be greatly appreciated. Is it crazy to think we can perform everything that "./configure", "make" and "make install" does oursleves without using those commands? Perhaps we do not need many of the things these commands do to set up NetSNMP? I obviously had no answers for my company on this issue, so I am asking for help from people who have gone through this before. --------------------------------- Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends. |
|
From: Steve F. <st...@un...> - 2007-06-07 19:34:43
|
On Thu, Jun 07, 2007 at 12:32:00PM -0700, Need Help wrote: > Ok, my company would like me to start discussing how to incorporate NetSNMP into the company's build environment. I explained the following stuff: Your company should probably retain a consultant experienced in these matters, because it's likely to rapidly wander outside the bounds of of the library itself, and what help you're likely to get here. Steve > - Indicated "./configure", "make" and "make install" were required for NetSNMP > - Indicated "snmp.conf" and "snmpd.conf" files exist to define stuff > - Indicated certain environment variables could be used if desired > - Indicated other stuff as well.... as much as I came across so far.... :>P > > During this discussion, the "build-production" people at my company informed me we can not perform the "configure" command as part of our "build process". Instead it would be necessary to understand exactly what the "configure" command (and I guess the "make" and "make install" commands as well) do "behind the scenes" so our build process and perform these exact steps ourselves. I was told we do not want to execute a script file with all of the required commands and options in it as well. > > Anyway, is this a common approach to integrating NetSNMP into a business application (ie: not using the standard setup commands/options as part of the command line or in a script file)? It scares me not to use the standard steps to get NetSNMP configured/running. Perhaps someone can explain to me whether this is weird or not. If so, then perhaps you can give me a quick overview as to how NetSNMP should "normally" be integrated in a build system. > > I understand no one knows how our build system works (neither do I), but any input into this topic would be greatly appreciated. > > Is it crazy to think we can perform everything that "./configure", "make" and "make install" does oursleves without using those commands? Perhaps we do not need many of the things these commands do to set up NetSNMP? > > I obviously had no answers for my company on this issue, so I am asking for help from people who have gone through this before. > > > > > > > > --------------------------------- > Don't be flakey. Get Yahoo! Mail for Mobile and > always stay connected to friends. > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Net-snmp-coders mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders -- Stephen J Friedl | Security Consultant | UNIX Wizard | +1 714 544-6561 www.unixwiz.net | Tustin, Calif. USA | Microsoft MVP | st...@un... |
|
From: Need H. <snm...@ya...> - 2007-06-07 19:48:59
|
Are you recommending we hire a "NetSNMP consultant" to come in and explain what can be done to integrate NetSNMP into our environment? If so, I can mention it to my management, but I would assume they would first like to know what each command does internally to the files and NetSNMP environment to see if they can simply mirror what these commands do. Anyway, the "build" people here are experienced with integrating other applications into the build environment. They typically figure out what all the "setup" commands do internally and then add this "underlying" functionality into the build process. I would assume it might be hard to determine what each individual option does internally or how each option affects the system configuration for use by NetSNMP, but this is what I have been asked to try and figure out. Actually, to start, I am only interested in figuring out how hard it would be to mirror what "Configure", "make" and "make install" do ...... Also, it would be nice to know whether it is a common practice to integrate NetSNMP into a build environment without using the "configure", "make", "make install", etc, etc.. commands which are normally used to get NetSNMP functioning properly. Steve Friedl <st...@un...> wrote: On Thu, Jun 07, 2007 at 12:32:00PM -0700, Need Help wrote: > Ok, my company would like me to start discussing how to incorporate NetSNMP into the company's build environment. I explained the following stuff: Your company should probably retain a consultant experienced in these matters, because it's likely to rapidly wander outside the bounds of of the library itself, and what help you're likely to get here. Steve > - Indicated "./configure", "make" and "make install" were required for NetSNMP > - Indicated "snmp.conf" and "snmpd.conf" files exist to define stuff > - Indicated certain environment variables could be used if desired > - Indicated other stuff as well.... as much as I came across so far.... :>P > > During this discussion, the "build-production" people at my company informed me we can not perform the "configure" command as part of our "build process". Instead it would be necessary to understand exactly what the "configure" command (and I guess the "make" and "make install" commands as well) do "behind the scenes" so our build process and perform these exact steps ourselves. I was told we do not want to execute a script file with all of the required commands and options in it as well. > > Anyway, is this a common approach to integrating NetSNMP into a business application (ie: not using the standard setup commands/options as part of the command line or in a script file)? It scares me not to use the standard steps to get NetSNMP configured/running. Perhaps someone can explain to me whether this is weird or not. If so, then perhaps you can give me a quick overview as to how NetSNMP should "normally" be integrated in a build system. > > I understand no one knows how our build system works (neither do I), but any input into this topic would be greatly appreciated. > > Is it crazy to think we can perform everything that "./configure", "make" and "make install" does oursleves without using those commands? Perhaps we do not need many of the things these commands do to set up NetSNMP? > > I obviously had no answers for my company on this issue, so I am asking for help from people who have gone through this before. > > > > > > > > --------------------------------- > Don't be flakey. Get Yahoo! Mail for Mobile and > always stay connected to friends. > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Net-snmp-coders mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders -- Stephen J Friedl | Security Consultant | UNIX Wizard | +1 714 544-6561 www.unixwiz.net | Tustin, Calif. USA | Microsoft MVP | st...@un... --------------------------------- Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends. |
|
From: Magnus F. <ma...@ly...> - 2007-06-07 22:34:02
|
On tor, 2007-06-07 at 12:48 -0700, Need Help wrote:
> Are you recommending we hire a "NetSNMP consultant" to come in and
> explain what can be done to integrate NetSNMP into our environment?
> If so, I can mention it to my management, but I would assume they
> would first like to know what each command does internally to the
> files and NetSNMP environment to see if they can simply mirror what
> these commands do.
>
> Anyway, the "build" people here are experienced with integrating other
> applications into the build environment. They typically figure out
> what all the "setup" commands do internally and then add this
> "underlying" functionality into the build process.
>
> I would assume it might be hard to determine what each individual
> option does internally or how each option affects the system
> configuration for use by NetSNMP, but this is what I have been asked
> to try and figure out. Actually, to start, I am only interested in
> figuring out how hard it would be to mirror what "Configure", "make"
> and "make install" do ......
>
> Also, it would be nice to know whether it is a common practice to
> integrate NetSNMP into a build environment without using the
> "configure", "make", "make install", etc, etc.. commands which are
> normally used to get NetSNMP functioning properly.
What I would do if I were to incorporate netsnmp in my build environment
would be to:
* Treat Net-SNMP as a third party component
This means that I do not build it as part of regular builds,
instead it is built once in a blue moon when there are upgrades
from the provider that are of interest to me.
* Integrate it in my build system based on net-snmp-config
The flags that have to be added are provided by net-snmp-config,
especially the --cflags and --libs options are of interest but
please do run it and read the output of the --help option.
* Only use configure, make, make install when I had a new target
platform or a new net-snmp version
I do not want to build net-snmp just because I wish to build my
product.
I suppose your build people could live with this and go on from there.
> Steve Friedl <st...@un...> wrote:
> On Thu, Jun 07, 2007 at 12:32:00PM -0700, Need Help wrote:
> > Ok, my company would like me to start discussing how to
> incorporate NetSNMP into the company's build environment. I
> explained the following stuff:
>
> Your company should probably retain a consultant experienced
> in these
> matters, because it's likely to rapidly wander outside the
> bounds of
> of the library itself, and what help you're likely to get
> here.
>
> Steve
>
>
> > - Indicated "./configure", "make" and "make install" were
> required for NetSNMP
> > - Indicated "snmp.conf" and "snmpd.conf" files exist to
> define stuff
> > - Indicated certain environment variables could be used if
> desired
> > - Indicated other stuff as well.... as much as I came across
> so far.... :>P
> >
> > During this discussion, the "build-production" people at my
> company informed me we can not perform the "configure" command
> as part of our "build process". Instead it would be necessary
> to understand exactly what the "configure" command (and I
> guess the "make" and "make install" commands as well) do
> "behind the scenes" so our build process and perform these
> exact steps ourselves. I was told we do not want to execute a
> script file with all of the required commands and options in
> it as well.
Somewhat extreme, but I can accept their position.
* configure checks various aspects of how your environment works
and adapts the net-snmp package to that.
* make compiles all source files based on the configure result.
* make install installs the finished result.
> > Anyway, is this a common approach to integrating NetSNMP
> into a business application (ie: not using the standard setup
> commands/options as part of the command line or in a script
> file)? It scares me not to use the standard steps to get
> NetSNMP configured/running. Perhaps someone can explain to me
> whether this is weird or not. If so, then perhaps you can give
> me a quick overview as to how NetSNMP should "normally" be
> integrated in a build system.
The important part is to differ between building net-snmp and building a
net-snmp client.
> > I understand no one knows how our build system works
> (neither do I), but any input into this topic would be greatly
> appreciated.
It is a pretty standard configure-based setup.
To build net-snmp you run configure; make; make install
To use net-snmp you just add the right include paths and libraries.
> > Is it crazy to think we can perform everything that
> "./configure", "make" and "make install" does oursleves
> without using those commands? Perhaps we do not need many of
> the things these commands do to set up NetSNMP?
Yes, it is crazy. There is no buisness value for you company in
reinventing that wheel.
> > I obviously had no answers for my company on this issue, so
> I am asking for help from people who have gone through this
> before.
/MF
|
|
From: Dave S. <D.T...@cs...> - 2007-06-07 20:32:00
|
On 07/06/07, Need Help <snm...@ya...> wrote: > Is it crazy to think we can perform everything that "./configure", "make" > and "make install" does oursleves without using those commands? Yes! You could perhaps set up the 'Makefile' and net-snmp-config.h files manually, but you'd need to run configure once first, to find out the appropriate settings. I suppose you could run "make" (and "make install") manually once, and capture the output. That output could then be used as a script to compile and install the software (having first been validated by your build production people). That might be acceptable to your company, but it feels like a lot of unnecessary work. If you don't trust the build procedure, why would you trust the code itself? How do they usually deal with installing open-source software? Dave |
|
From: Need H. <snm...@ya...> - 2007-06-07 20:48:50
|
I am not knowledgeable in this area at all. I really can not comment on this. Based on the meeting we had, I was under the impression they would prefer not to use "configure" as part of the build sequence. Perhaps using "configure" outside of the build sequence to simply obtain changed files which could then be incorporated into the build sequence would be possible, if this is what you are recommending.
I do not think it has anything to do with not trusted the build procedure, but has more to do with building our environment might not allow for a "configure" script to run and completely execute perhaps? I do not know. I am sure it has nothing to do with not trusting the build of "configure" though.
Dave Shield <D.T...@cs...> wrote: On 07/06/07, Need Help wrote:
> Is it crazy to think we can perform everything that "./configure", "make"
> and "make install" does oursleves without using those commands?
Yes!
You could perhaps set up the 'Makefile' and net-snmp-config.h files
manually, but you'd need to run configure once first, to find out the
appropriate settings.
I suppose you could run "make" (and "make install") manually once,
and capture the output. That output could then be used as a script
to compile and install the software (having first been validated by
your build production people).
That might be acceptable to your company, but it feels like a lot
of unnecessary work. If you don't trust the build procedure, why
would you trust the code itself?
How do they usually deal with installing open-source software?
Dave
---------------------------------
Building a website is a piece of cake.
Yahoo! Small Business gives you all the tools to get online. |
|
From: Bruce S. <Bru...@go...> - 2007-06-07 22:32:23
|
>I am not knowledgeable in this area at all. =20 =20 Then maybe we should be talking to someone who is.=20 This email and any files transmitted with it are confidential and intende= d solely for the use of the individual or entity to whom they are address= ed. If you have received this email in error please notify the system man= ager. This message contains confidential information and is intended only= for the individual named. If you are not the named addressee you should = not disseminate, distribute or copy this e-mail. |
|
From: Need H. <snm...@ya...> - 2007-06-08 13:59:34
|
Yes, and eventually it might come to that, but in the meantime, I am the only person which is assigned to handle the SNMP integration work. No oen is given time to do this task yet. We just want to start looking into what it would take, and I am the person who is trying to gather some data/ideas on how to make this happen. Eventually, the build people will be getting involved if required in the future.
I still have to get NetSNMP functioning for our MIB first, before we try to integrate it into our environment..... :>P
Thanks for the information on this issue.
Bruce Shaw <Bru...@go...> wrote: >I am not knowledgeable in this area at all.
Then maybe we should be talking to someone who is.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
---------------------------------
Be a better Heartthrob. Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out. |
|
From: Robert S. <rs...@fr...> - 2007-06-07 20:36:46
|
On Thu, 7 Jun 2007 12:32:00 -0700 (PDT) Need wrote: NH> During this discussion, the "build-production" people at my company informed me we can not perform the "configure" command as part of our "build process". Unless you have a static fixed environment, they are pretty much nuts. Replicating configure would be stupidity on a grand scale. A slightly less stupid idea would be to take the output of configure (net-snmp-config.h and Makefile, and a few C files and headers) and make them part of a static package. But any change in the build environment would mean that the process would have to be repeated. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X