> The layout of build/output looks useable, and I can produce debs from that. > I'll be moving stuff around, to make it fit properly in FHS. I'll be making > some things into symlinks, to give jboss a correct view on the world. In > other cases, I'll modify the configuration files to access the correct > locations directly.
What changes need to be make to make things fit into FHS? > Now, to the biggest issue with all this. Could the final jboss tarball that > is created, *NOT* have any external source? I can understand having a tarball What do you mean external source? > that does have this source, but could it be called jboss-bundle-src.tar.gz, or > something. If there is no source tarball that is in this pristince state, > then I will not be able to upload jboss to Debian, because then it would mean > that Debian is distributing non-free software, which is not allowed. Can you be more specific about what parts of the current 3.0 dist are not allowed? > Making debs of course, doesn't really matter about what is included and what > isn't. But for actual upload to the Debian archive(and all its mirrors), I > *NEED* this non-free code and external code removed from the source tarball. > Even if this means the build system contains broken references to these > missing files, that is fine. The build system probably won't work with "broken" anything. What non-free code and external code are you talking about? --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
