On Friday 11 December 2009 05:41:41 pm David Leverton wrote: > On Friday 11 December 2009 23:27:45 Sterling X. Winter wrote: > > The solution we settled on was to create a new package > > (dev-java/java-env) to handle the env.d files, and add that as a > > build+run dep to virtual/jdk. > > Wouldn't it be better to add the dep to the JDKs/JREs themselves? > Presumably the environment variables are still needed if the user installs > a JDK but nothing depending on the virtual.
A user who installs a JDK directly rather than through virtual/jdk might have environment requirements that diverge from the common use case, and they're somewhat more likely to be prepared to deal with that and less likely to want java-env. At the other end, most users who just need "a JDK, any JDK" and install it via virtual/jdk would probably appreciate how java-env makes things less complicated. Your suggestion also makes sense though, and I admit I don't have a strong preference either way. _______________________________________________ Exherbo-dev mailing list [email protected] http://lists.exherbo.org/mailman/listinfo/exherbo-dev
