On Fri, Nov 20, 2009 at 11:29 AM, Ben Walton <[email protected]> wrote: > Excerpts from Philip Brown's message of Fri Nov 20 14:25:02 -0500 2009: >> >> for example, one of them that you named, CSWshutils, has 3 packages >> depending on it. > > Ok, bigger job, but the payoff is worthwhile. >
A thought: one way to handle this, over a LONG term, would be to define a virtual package CSWcoreutils (hmm.. or CSWgcoreutils, or CSWgnucoreutils might be better) which depended on all the ones it will eventually replace. Then you could focus on updating dependancies to point at the new package, over time. THEN, once things are finally all pointing at the new package, you would then be free and clear to do your original planned "easy way". Contrariwise, you could compile coreutils, but actually have it split up into the old-style packages, release it now as-is (replacing those older CSWgxxx packages), and that wya, leave the dependancies alone :-) _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
