In article <[EMAIL PROTECTED]> you wrote:
> I was looking for a more generic approach, I guess. One that breaks down
> the basic concepts, caveats, concerns, etc. Looking at it now, I realize
> Free Software and commercial software will have different emphasises, even
> at this level.
For one
>
> I take it from your "exporting our code" statement that your software
> will be Free Software? (It makes a difference because your packaging
> strategy will be different depending on whether or not the software is
> com
>
> --
> Kevin B. McCarty <[EMAIL PROTECTED]> Physics Department
> WWW:
Gilbert, Joseph wrote:
> We are looking at now exporting our code and making it useful to a wider
> client base. This obviously will mean that the software packages will have
> to be built as .deb, .rpms, tarballs and whatever else will be needed. I
> have been told that I will likely be respons
On Wed, 2005-03-02 at 15:19 -0800, Gilbert, Joseph wrote:
> Hi guys,
>
> I work for a software company that up until now has developed software,
> mostly written in Java, that is deployed inhouse to servers that are
> administering internally.
>
> We are looking at now exporting our code and maki
Hi guys,
I work for a software company that up until now has developed software,
mostly written in Java, that is deployed inhouse to servers that are
administering internally.
We are looking at now exporting our code and making it useful to a wider
client base. This obviously will mean that the
5 matches
Mail list logo