Re: How to package and release for iSeries?

Charles,

Thank you for your reply.

I understand your point about controlling what gets installed on your 
machines, but locking down the SAVE/RESTORE commands seems somewhat absurd 
to me.  The FTPAPI example you provided illustrates the weakness of this 
approach.  Although I was not able to install FTPAPI using the SAVF object 
-- because I am not authorized to use the ALWOBJDIF parameter -- I was 
able to install it using the XML installer.  So, at the end of the day, I 
can install any software I want.  The SAVE/RESTORE commands I cannot run 
are just an annoyance, not an obstacle.  IMHO, that hardly qualifies as a 
security mechanism.  Anyway, my goal is not to start an argument about 
what is right or what is secure, but to release OSS in a user-friendly 
way.

I really liked the XML Installer approach used by Scott.  It is quick, 
straightforward and yet flexible.  I am going to try that for my OSS 
project.

Thanks a lot for the pointer!

Regards.

antoine



Antoine,

I don't have an answer for you, but wanted to comment on what you said
about using SAVF.

"A SAVF file would keep the meta-information, but I have had several bad
experiences with SAVF that I 
could not restore because of authority problems (I do not have a
security officer profile)."

Then you probably shouldn't be trying to load the software in the first
place.  While you shouldn't need SECOFR, you do have to have authority
to SAVE/RESTORE.  If you don't then somebody else at your company should
have been the one to install the software.

I know I wouldn't want my users to be able to download and install
anything they wanted.  If they need something, they need to make a
request for it and if the request is approved, I'm happy to load what is
needed.


Actually, as I think about it, I do have an answer to your question.
Though like everything else I've ever seen for the 400, it uses save
files.

Scott Klement provides his FTPAPI via three different install methods.
One of them, is an XML install routine.  His web page is here:
http://www.scottklement.com/ftpapi/

Though it seems to be down right now.


Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: oss400-bounces-Zwy7GipZuJhWk0Htik3J/[email protected] 
> [mailto:oss400-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]] On Behalf Of 
> [email protected]
> Sent: Tuesday, July 04, 2006 5:53 AM
> To: oss400-Zwy7GipZuJhWk0Htik3J/[email protected]
> Subject: [OSS400] How to package and release for iSeries?
> 
> (It looks like my first email did not go through. Sorry if this is a 
> duplicate.)
> 
> Hello,
> 
> I would like to know what you think is the best way to 
> package and release 
> OSS for the iSeries platform?  Is there some OSS project you think is 
> remarkable from this point of view?  Are some OSS-hosting sites more 
> 'iSeries friendly' than others?  What kind of issues do you 
> run into when 
> you try to install, compile and run OSS on your iSeries?
> 
> For PCs, it is straightforward.  Just put your sources in a 
> CVS or SVN 
> repository, and anybody can download and build the software. 
> But for the 
> iSeries, doing it that way would mean losing all 
> meta-information like 
> source type (e.g., RPGLE) and comments.  A SAVF file would keep the 
> meta-information, but I have had several bad experiences with 
> SAVF that I 
> could not restore because of authority problems (I do not 
> have a security 
> officer profile).
> 
> Thank you for your help.
> 
> Regards.
> 
> antoine


Ensemble adoptons des gestes responsables : N'imprimez ce mail que si necessaire.

Les informations contenues dans ce message et les pieces jointes (ci-apres denomme le message) sont confidentielles et peuvent etre couvertes par le secret professionnel. Si vous n'etes pas le destinataire de ce message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez recu ce message par erreur, nous vous remercions de le supprimer de votre systeme, ainsi que toutes ses copies, et d'en avertir immediatement HSBC France et ses filiales par message de retour. Il est impossible de garantir que les communications par messagerie electronique arrivent en temps utile, sont securisees ou denuees de toute erreur, alteration, falsification ou virus. En consequence, HSBC France et ses filiales declinent toute responsabilite du fait des erreurs, alterations, falsifications ou omissions qui pourraient en resulter.

Consider the environment before printing this mail.

The information contained in this e-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message by error, please delete it and all copies from your system and notify the sender immediately by return e-mail. E-mail communications cannot be guaranteed to be timely secure, error or virus-free. The sender does not accept liability for any errors or omissions which arise as a result.

_______________________________________________
This is the Open Source Software for the AS400/iSeries (OSS400) mailing list
To post a message email: OSS400-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/oss400
or email: OSS400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/oss400.