id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc,fix_version,see_also 374,clean up redundancies in debathena-thirdparty,geofft,kaduk,"This is a separate issue from removing unwanted packages from debathena-thirdparty: there are a couple of cases in which our metapackages depend on one package and a couple of that package's dependencies, which can be simplified. -dev packages and their non-dev library partners are a good example of this. This should not be a change in practical function of the package. There are also a couple of cases in which our metapackages depend on one package and a couple of that package's recommendations: for instance, we could replace (almost?) all of the boost packages in thirdparty-libraries with just libboost-dev. This would be a significant cleanup, but a slight functional change. It's worth considering if there are reasons to keep these packages as hard dependencies; one technical reason to do so is that recommendations are never resatisfied if they happen not to be satisfied when the package is first installed (see #373). See that ticket and also #372 for discussion of making everything in -thirdparty recommendations, which, if implementable, would make this option clearly okay.",task,closed,low,Current Semester,--,fixed,,alexp,,