On 11-01-04 10:31 AM, Howard Butler wrote:
No problem. I'd be happy to remove the liblas-devel and liblas-python packages as well and collate them into a single package as well. I was just following the seemingly established pattern. If we are not so rigorously tied to it, it makes it much easier for users to only have to click one thing.
Howard, The liblas-python package might be a useful distinction in that it separates the dependency on the fairly heavy Python package. But it's your call. I imagine liblas-devel could be rolled into liblas painlessly. I still have a few -devel packages. Some were from before I grew concerned about proliferation and at least one is for a package with over a MB of -devel stuff. Best regards, -- ---------------------------------------+-------------------------------------- I set the clouds in motion - turn up | Frank Warmerdam, [email protected] light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush | Geospatial Programmer for Rent _______________________________________________ osgeo4w-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/osgeo4w-dev
