HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Best practices for program distribution - OR -...
Operating System - HP-UX
1837791
Members
3045
Online
110120
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2003 08:28 AM
02-05-2003 08:28 AM
Best practices for program distribution - OR - No such binary version (c, c++)?
Hi, folks.
I've just had a vendor/developer come to me and tell me something I can't quite believe. I received from said vendor a tarball of new scripts and binaries to install - with no installation instructions outside of, "Install these."
So, I asked for some basic items: version number, cksum, directory, ownerships, and permissions. What else do I need to ask for? Environment changes?
My vendor has come back and said, basically, that I don't need ownership/permission information. To the really strange part ... after some exposition about headers and libraries, this vendor said:
???Therefore, there is no version for a binary.???
Okay, I'd like to avoid jumping to conclusions, and I'd just like to check myself.
Is there such a thing as a binary "version" for binaries? I think there should AT A MINIMUM be a build version, regardless of the underlying headers and libraries - regardless of the language in question. I don't have access to the source, and some change control is necessary to avoid serious headaches!
What are the best practices for software distribution, and what are reasonable things for me to request of my vendor?
Thanks.
I've just had a vendor/developer come to me and tell me something I can't quite believe. I received from said vendor a tarball of new scripts and binaries to install - with no installation instructions outside of, "Install these."
So, I asked for some basic items: version number, cksum, directory, ownerships, and permissions. What else do I need to ask for? Environment changes?
My vendor has come back and said, basically, that I don't need ownership/permission information. To the really strange part ... after some exposition about headers and libraries, this vendor said:
???Therefore, there is no version for a binary.???
Okay, I'd like to avoid jumping to conclusions, and I'd just like to check myself.
Is there such a thing as a binary "version" for binaries? I think there should AT A MINIMUM be a build version, regardless of the underlying headers and libraries - regardless of the language in question. I don't have access to the source, and some change control is necessary to avoid serious headaches!
What are the best practices for software distribution, and what are reasonable things for me to request of my vendor?
Thanks.
Command-Line Junkie
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2003 08:36 AM
02-05-2003 08:36 AM
Re: Best practices for program distribution - OR - No such binary version (c, c++)?
Hi,
To install any s/w on HP it should be in binary or .depot form. check the vendor s/w in which format it is.
If the vendor insist, do the swinstall -s , if the s/w is not in binary , swinstall throws the errors
To install any s/w on HP it should be in binary or .depot form. check the vendor s/w in which format it is.
If the vendor insist, do the swinstall -s
never give up
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2003 08:48 AM
02-05-2003 08:48 AM
Re: Best practices for program distribution - OR - No such binary version (c, c++)?
It all depends on the customer, the vendor, and their mutual trust. We have some customers that don't care what's on their computer as long as it works, and I know about vendors that just state a random version number if asked for just to satisfy the customer.
Of course good software requires version control, but some packages are built out of many sources. All these sources might have version control, but the complete thingy might not. Stating all the versions of the subcomponents would probably not satisfy a customer either.
Just to add a ??? 0.02 to the confusion :)
Enjoy, have FUN! H.Merijn
Of course good software requires version control, but some packages are built out of many sources. All these sources might have version control, but the complete thingy might not. Stating all the versions of the subcomponents would probably not satisfy a customer either.
Just to add a ??? 0.02 to the confusion :)
Enjoy, have FUN! H.Merijn
Enjoy, Have FUN! H.Merijn
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP