On 8/14/2014 3:52 AM, Mateusz Viste wrote:
> Hi Ulrich,
>
> Thanks for your feedback!
>
> On 08/14/2014 12:05 AM, Ulrich wrote:
>> FDNPKG installs the MTCP programs into C:\FDOS\MTCP instead of C:\FDOS\BIN.
> This is not really about FDNPKG, but more about "how packages are
> structured". Indeed, I tend to avoid putting to much stuff into
> %FREEDOS%\BIN, and only put there stuff that is supposed to be part of
> the FreeDOS "core" (ie BASE, that is similar functionality than what
> MSDOS was providing).
>
> Now the question is where to put any 3rd party apps that are still
> supposed to be callable from anywhere in the directories tree? One
> option could be to create another "BIN-like" directory for these (which
> would be close to what Linux does - sbin vs bin - but I'm not sure this
> will look natural to DOS folks), or (and this is my favorite so far),
> install any 3rd party progs as usual program (dedicated directory), but
> add a "link" to special directory (say, %FREEDOS%\links for instance).
> The link would be a simple BAT file that would call the real program.
> This is actually a method I'm using on my own PC.
>
> Any other thoughts?
>

I had explicitly asked for mTCP to be packaged in a separate directory.  
mTCP includes documentation and configuration files, and having those 
lumped in with many many other files would it more difficult to find 
them if you did not know the exact name of what you were looking for.  
It also prevents naming conflicts.

mTCP should be callable from anywhere, not just its own directory. I 
think this is an appropriate use of the PATH environment variable.

Small, well known utilities are safe to put together in a BIN-like 
directory.  Utilities that require multiple files are probably better 
isolated into their own directory.


Mike

------------------------------------------------------------------------------
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to