> Does the stuff in j2ee and naming depend on other jboss items? Do they depend
> on the jboss module? If no, then I started at the wrong spot.
If you look in each build.xml there is a target called '_configure-modules',
this section shows the dependency on other modules (or in the case of the
build module shows how the modules are organized).
> Is everything in thirdparty exact copies of external libraries, that get
> built, or just checked in pre-compiled version, or a mixture of the two?
Everything from thirdparty and tools are pre-compiled.
> In either case, since they are third party modules, and not part of jboss,
> they can not be packaged with jboss in Debian.
Fine, as long as you make for sure that there are packages available that
contains the *exact* version of these libraries (version appropriately so
that things don't break when they are updated).
> If jboss has patched these upstream sources, have the patches then been sent
> upstream?
Nothing in thirdparty has been patched. They are the same files from
downloaded distributions.
> I'm not building a single jboss deb. What I have done for 2.4, is make
> separate debs, split along the same lines as each top-level directory in the
> 2.4.3 tarball.
I am not interested in the .deb'ification of 2.4.x at all. I would expect
that the package structure of 2.4 would be mostly if not completly different
than 3.0.
* * *
I am interested in the creation of .deb's to make it easier for people to
get/install/use JBoss. I am very concerned that what you are doing will
cause support and maintenece problems. I would rather like to avoid having
differing instructions for debian and non-debian users. I would also like
to avoid help me emails about users who have the wrong version of
thirdparty .deb packages installed... especially when I don't really know
who makes and maintains them.
I think it would be really cool if a debian user could 'apt-get jboss' and
in a few minutes/seconds have a functional server which they could start
working with right away.
I also think that there are huge maintenece issues envolved with making this
happen. Thus I would lean twords a .deb building system that took worked
off our existing release and made use of the support files which are
contained there.
If these maintence problems are not resolved, then each time a new release
comes out there will be problems when users upgrade, which might lead them
away from JBoss... or may lead them to simply download the .tar.gz and work
from there (which isn't soo bad, but just wasted yours and my time over all
of this).
The only way I can see that this will fly at all would be if
1) the building of jboss .deb's was integrated into the jboss build system
(removing the dependency on you or any other .deb packager to build them)
2) proving that there are active/reliable maintainers of packages
for ALL the thirdparty libs required or generating those libs from the
jboss thirdparty repository
3) ensureing that any FHS or anyother debian specific changes that need to
be made to the release do not have ANY effect on the servers operation
and do not make the administration and support of the server any
different than the .tar.gz/.zip release.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
