Working on the proposal for central repo design and would like to solicit feedback on how everyone is using PathEnv.
Does anyone use PathEnv with multiple directories (other than just boot and working)?
What kind of setup have your found effective for where you stick core/boot and your working code?
Any specific comments on what works well and what doesn't work well with PathEnv?
Most likely the new repo design will include a replacement for PathEnv called RepoEnv which allows selection of pods from a more sophisticated database than a simple flat directory.
tcolarThu 28 Apr 2011
I don't use PathEnv so no comment on that.
One thing I'd like is for the proposed repo to also handle dependencies and libraries like SWT and jar files(example mysql), having to put those in specific locations within the fan runtime is impractical and kinda fragile, and i've had issues with that (More difficult setup, classpath/versions clash etc...)
lbertrandSat 30 Apr 2011
I use pathEnv for development - keep the fantom distribution clean and use a working development env for all my development.
And I think that for external dependencies coming from global repository, I would like to keep my working env free of those - so either the external dependencies are downloaded into the main fantom env distro or into a third env...
I prefer it to be into a third env as this means when I download and get a new fantom distro the dependencies downloaded do not have to be downloaded again!
For a user, I still don't really know/understand how to deploy a Fantom application. Should they download the main Fantom distro and then automatically can install an application using the main web repository, which also pull the dependencies into a predefined place... Was wondering even if Fantom could be updated the same way... New sys pod in version 1.1 is released and an application depend on it so automatically download the new version of sys pod... So maybe, an end user just need to get the installer application, and then all is managed from it, even the main Fantom distro.
brian Thu 28 Apr 2011
Working on the proposal for central repo design and would like to solicit feedback on how everyone is using PathEnv.
Most likely the new repo design will include a replacement for
PathEnvcalledRepoEnvwhich allows selection of pods from a more sophisticated database than a simple flat directory.tcolar Thu 28 Apr 2011
I don't use PathEnv so no comment on that.
One thing I'd like is for the proposed repo to also handle dependencies and libraries like SWT and jar files(example mysql), having to put those in specific locations within the fan runtime is impractical and kinda fragile, and i've had issues with that (More difficult setup, classpath/versions clash etc...)
lbertrand Sat 30 Apr 2011
I use pathEnv for development - keep the fantom distribution clean and use a working development env for all my development.
And I think that for external dependencies coming from global repository, I would like to keep my working env free of those - so either the external dependencies are downloaded into the main fantom env distro or into a third env...
I prefer it to be into a third env as this means when I download and get a new fantom distro the dependencies downloaded do not have to be downloaded again!
For a user, I still don't really know/understand how to deploy a Fantom application. Should they download the main Fantom distro and then automatically can install an application using the main web repository, which also pull the dependencies into a predefined place... Was wondering even if Fantom could be updated the same way... New sys pod in version 1.1 is released and an application depend on it so automatically download the new version of sys pod... So maybe, an end user just need to get the installer application, and then all is managed from it, even the main Fantom distro.