Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
4 edited tags
| link
3 added 240 characters in body
source | link

I need to determine an appropriate directory naming structure for a package management system. The original directory structure was not POSIX-compliant in any way and certainly not UNIX-style (you'll notice it's similar to GoboLinux). The structure looked somewhat like this:

  • /Applications - applications for users (but that users have not themselves installed)
  • /System/AppResolve - application resolution (effectively /bin)
  • /System/LibResolve - library resolution (effectively /lib)
  • /System/Utilities/Applications - essential applications for system operation
  • /System/Utilities/Libraries - essential libraries for system operation

Now I need to find a way to represent this directory structure on a more UNIX-like system. AppResolve and LibResolve aren't an issue since /lib and /bin work fine for this, the issue is with the other directories.

Under each of the other directories, applications live in their own folder, so for example you might have this kind of path:

/System/Utilities/Applications/Tar/1.22/bin/tar

Of course, the /bin/tar symlink would resolve to this binary.

So the question is this, I need to take this kind of structure and rearrange it to fit within the UNIX-style of naming directories (particularly so that it works with the existing structure on Linux). I thought of the following, but I think it's repetitive and not very nice:

  • /usr/app/user/applications/...
  • /usr/app/system/applications/Tar/1.22/bin/tar
  • /usr/app/system/libraries/...

Suggestions?

FOR CLARIFICATION: This isn't asking for a mapping to existing UNIX directories; it's asking for the most appropriate leading path for those "user" and "system" directories given the UNIX-naming convention (3-letter directories, etc.)

I need to determine an appropriate directory naming structure for a package management system. The original directory structure was not POSIX-compliant in any way and certainly not UNIX-style (you'll notice it's similar to GoboLinux). The structure looked somewhat like this:

  • /Applications - applications for users (but that users have not themselves installed)
  • /System/AppResolve - application resolution (effectively /bin)
  • /System/LibResolve - library resolution (effectively /lib)
  • /System/Utilities/Applications - essential applications for system operation
  • /System/Utilities/Libraries - essential libraries for system operation

Now I need to find a way to represent this directory structure on a more UNIX-like system. AppResolve and LibResolve aren't an issue since /lib and /bin work fine for this, the issue is with the other directories.

Under each of the other directories, applications live in their own folder, so for example you might have this kind of path:

/System/Utilities/Applications/Tar/1.22/bin/tar

Of course, the /bin/tar symlink would resolve to this binary.

So the question is this, I need to take this kind of structure and rearrange it to fit within the UNIX-style of naming directories (particularly so that it works with the existing structure on Linux). I thought of the following, but I think it's repetitive and not very nice:

  • /usr/app/user/applications/...
  • /usr/app/system/applications/Tar/1.22/bin/tar
  • /usr/app/system/libraries/...

Suggestions?

I need to determine an appropriate directory naming structure for a package management system. The original directory structure was not POSIX-compliant in any way and certainly not UNIX-style (you'll notice it's similar to GoboLinux). The structure looked somewhat like this:

  • /Applications - applications for users (but that users have not themselves installed)
  • /System/AppResolve - application resolution (effectively /bin)
  • /System/LibResolve - library resolution (effectively /lib)
  • /System/Utilities/Applications - essential applications for system operation
  • /System/Utilities/Libraries - essential libraries for system operation

Now I need to find a way to represent this directory structure on a more UNIX-like system. AppResolve and LibResolve aren't an issue since /lib and /bin work fine for this, the issue is with the other directories.

Under each of the other directories, applications live in their own folder, so for example you might have this kind of path:

/System/Utilities/Applications/Tar/1.22/bin/tar

Of course, the /bin/tar symlink would resolve to this binary.

So the question is this, I need to take this kind of structure and rearrange it to fit within the UNIX-style of naming directories (particularly so that it works with the existing structure on Linux). I thought of the following, but I think it's repetitive and not very nice:

  • /usr/app/user/applications/...
  • /usr/app/system/applications/Tar/1.22/bin/tar
  • /usr/app/system/libraries/...

Suggestions?

FOR CLARIFICATION: This isn't asking for a mapping to existing UNIX directories; it's asking for the most appropriate leading path for those "user" and "system" directories given the UNIX-naming convention (3-letter directories, etc.)

2 added 30 characters in body
source | link

I need to determine an appropriate directory naming structure for a package management system. TheThe original directory structure was not POSIX-compliant in any way and certainly not UNIX-style (you'll notice it's similar to GoboLinux). The structure looked somewhat like this:

  • /Applications/Applications - applications for users (but that users have not themselves installed)
  • /System/AppResolve/System/AppResolve - application resolution (effectively /bin/bin)
  • /System/LibResolve/System/LibResolve - library resolution (effectively /lib/lib)
  • /System/Utilities/Applications/System/Utilities/Applications - essential applications for system operation
  • /System/Utilities/Libraries/System/Utilities/Libraries - essential libraries for system operation

Now I need to find a way to represent this directory structure on a more UNIX-like system. AppResolve and LibResolve aren't an issue since /lib/lib and /bin/bin work fine for this, the issue is with the other directories.

Under each of the other directories, applications live in their own folder, so for example you might have this kind of path:

/System/Utilities/Applications/Tar/1.22/bin/tar

/System/Utilities/Applications/Tar/1.22/bin/tar

Of course, the /bin/tar/bin/tar symlink would resolve to this binary.

So the question is this, I need to take this kind of structure and rearrange it to fit within the UNIX-style of naming directories (particularly so that it works with the existing structure on Linux). I thought of the following, but I think it's repetitive and not very nice:

  • /usr/app/user/applications/.../usr/app/user/applications/...
  • /usr/app/system/applications/Tar/1.22/bin/tar/usr/app/system/applications/Tar/1.22/bin/tar
  • /usr/app/system/libraries/.../usr/app/system/libraries/...

Suggestions?

I need to determine an appropriate directory naming structure for a package management system. The original directory structure was not POSIX-compliant in any way and certainly not UNIX-style (you'll notice it's similar to GoboLinux). The structure looked somewhat like this:

  • /Applications - applications for users (but that users have not themselves installed)
  • /System/AppResolve - application resolution (effectively /bin)
  • /System/LibResolve - library resolution (effectively /lib)
  • /System/Utilities/Applications - essential applications for system operation
  • /System/Utilities/Libraries - essential libraries for system operation

Now I need to find a way to represent this directory structure on a more UNIX-like system. AppResolve and LibResolve aren't an issue since /lib and /bin work fine for this, the issue is with the other directories.

Under each of the other directories, applications live in their own folder, so for example you might have this kind of path:

/System/Utilities/Applications/Tar/1.22/bin/tar

Of course, the /bin/tar symlink would resolve to this binary.

So the question is this, I need to take this kind of structure and rearrange it to fit within the UNIX-style of naming directories (particularly so that it works with the existing structure on Linux). I thought of the following, but I think it's repetitive and not very nice:

  • /usr/app/user/applications/...
  • /usr/app/system/applications/Tar/1.22/bin/tar
  • /usr/app/system/libraries/...

Suggestions?

I need to determine an appropriate directory naming structure for a package management system. The original directory structure was not POSIX-compliant in any way and certainly not UNIX-style (you'll notice it's similar to GoboLinux). The structure looked somewhat like this:

  • /Applications - applications for users (but that users have not themselves installed)
  • /System/AppResolve - application resolution (effectively /bin)
  • /System/LibResolve - library resolution (effectively /lib)
  • /System/Utilities/Applications - essential applications for system operation
  • /System/Utilities/Libraries - essential libraries for system operation

Now I need to find a way to represent this directory structure on a more UNIX-like system. AppResolve and LibResolve aren't an issue since /lib and /bin work fine for this, the issue is with the other directories.

Under each of the other directories, applications live in their own folder, so for example you might have this kind of path:

/System/Utilities/Applications/Tar/1.22/bin/tar

Of course, the /bin/tar symlink would resolve to this binary.

So the question is this, I need to take this kind of structure and rearrange it to fit within the UNIX-style of naming directories (particularly so that it works with the existing structure on Linux). I thought of the following, but I think it's repetitive and not very nice:

  • /usr/app/user/applications/...
  • /usr/app/system/applications/Tar/1.22/bin/tar
  • /usr/app/system/libraries/...

Suggestions?

1
source | link