On Thu, 2005-08-18 at 11:20, Joerg Schilling wrote:
What we need is an infrastructure for a build system.
Neither Sunfreeware not Blastwave has this as they both
supply only binaries.
Having a buld system that deals with fetching the original
soruces (or at least documenting the URL),
On Wed, 2005-07-27 at 11:52, Joerg Schilling wrote:
Fetching the JDS sources was a nightmare (I hat to do approx. 300 mouse
clicks).
I asume that unpacking the sources will take a whole day ad the sources are
in pkgadd format.
Hmm... sorry for that... The idea was that people won't
Hi Rod,
Thanks for the detailed response.
Of course I agree that it's better to avoid the problem by
carefully controlling public interface changes. However more
and more software in Solaris comes from external sources
and while we can work with community maintainers and try
and make sure they
Hi John,
On Wed, 2005-07-20 at 19:31, John Plocher wrote:
Without this ability to manage the evolution of shared components,
it becomes extremely difficult to reuse them, because asynchronous
development almost guarantees that a change to the shared component
will break a consumer, and that
I feel like it's time to mention my baby: pkgbuild
(pkgbuild.sf.net), which is an rpmbuild replacement that
produces Solaris SVr4 packages. This is what we use for
building JDS/Solaris (all GNOME, Mozilla, Evolution, APOC).
We have rpm spec files [with a few enhancements], patches
and community
