On Monday, October 17, 2016 3:13:32 PM EDT M. J. Everitt wrote: > On 17/10/16 15:09, Kristian Fiskerstrand wrote: > > On 10/17/2016 04:04 PM, William L. Thomson Jr. wrote: > >> Even if we have a list, what next? There are reasons why they are not > >> packaged from source, and that will not change. Good to be aware, but > >> without any sort of plan or means to address. Not sure it will matter. > > > > The list would be helpful for discussions in any case to know the scope, > > instead of making mountains out of molehills
I do not think it will be helpful, but here are some. I can see about producing a complete list but it requires time. Knowing there are some and more are being added should be enough. Again even knowing this does not address the problem of why? The reasons for the packages may differ, and I do not claim to know details about each, as to the reason why -bin vs from source. For Java based ones I know why, lots of dependencies not packaged. app-misc/rundeck-cli-bin net-p2p/go-ipfs-bin dev-util/artifactory-bin dev-util/jenkins-bin sci-misc/netlogo-bin sci-libs/openfoam-bin games-util/pogo-manager-bin dev-python/pypy3-bin dev-python/pypy-bin app-admin/filebeat-bin app-admin/logstash-bin app-text/jabref-bin app-backup/spideroak-bin ? dev-java/maven-bin (requires bootstrapping, need maven to build maven) If packages like Hadoop, Zookeeper, Wildfly, and others were added, they would likely be -bin as well. Several of these are quite large complex packages. -- William L. Thomson Jr.
signature.asc
Description: This is a digitally signed message part.
