Faxien has issues with the way in which it manages ERTS versions. The first issue I think is that it manages ERTS versions. I think the external interface needs to be Erlang versions and that we need to hid ERTS versions from people to a great extent. What this email contains are a number of issues and use cases where the current management is a problem.
1. Download the bootstrapper and the automatic upgrade of Faxien does not give you the latest version only the latest version for the ERTS versions that the bootstrapper can see. This results in multiple upgrades being required to get to the latest version. 2. Company X states that Erlang version R12B-5 is the standard for the company. Employee X runs faxien ia <some-app-or-release> and gets a package for the latest greatest that faxien knows about which is for Erlang version R13B02-1 3. Company X states that sinan-.0.11.2.3 is the defacto standard build system version. Users have no way of pinning that version and preventing an accidental upgrade. 4. Company X wants to stay on the R12B-X line in general. They can now specify a range but it is confusing becuase they must use Erts Versions and can't use Erlang versions. There are probably other use cases that exist around managing packages and versions that we need to think about. Any more ideas are welcome. Zishan and I, and anyone else that wants to join are going to start iterating on this problem once we come up with a design. Cheers, Martin -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
