search for: iceutil

...ser convenience for developer > convenience, which IMHO is usually a bad trade. > > I'd vote to merge the modules into one, but otherwise either keep the > status quo until subversion gets upgraded, or maybe add a checkout > script. It's a nuisance to check out three things (iceutil, m4, and > your project) to work on one, but it's not that much of a nuisance, > and checkout isn't a frequent operation. Grouping the modules together is not a problem, however I agree with Brendan here that they should still be linked into icecast and ices statically both for '...

...ll this just sacrifices user convenience for developer convenience, which IMHO is usually a bad trade. I'd vote to merge the modules into one, but otherwise either keep the status quo until subversion gets upgraded, or maybe add a checkout script. It's a nuisance to check out three things (iceutil, m4, and your project) to work on one, but it's not that much of a nuisance, and checkout isn't a frequent operation. -b --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icec...

with our new move to Subversion, we apparently lost the ability to easily link submodules into a single higher-level module (such as icecast)...in the old CVS repository, icecast consisted of a handful of modules, icecast and other modules, which are shared by icecast and ices : avl httpp log net thread timing in the new Subversion repository, they are still kept as separate modules,