Hi, I am looking for suggestion how to split "legacy package". We have several such cases, but the most simple case is network/ftp package (originally SUNWbip/SUNWbipr). It contains several deliverables:
etc/default/ftp (from SUNWbipr) usr/bin/ftp (from SUNWbip) usr/sbin/ping (from SUNWbip) Even before SVR4->IPS move, there was old request to split ftp cli from SUNWbip but nobody did it. After move and rename, it should go the other way (and it is more urgent because of package name). So I would like to remove ping from network/ftp package and move it to some new package network/ping I see 2 problems now: 1) update from previous build - how to enforce installation of network/ping during update (to keep ping installed if it was already) but not make network/ping mandatory dependency of network/ftp (to allow separate install of them) - in some systems I saw that they created 2 new packages and made the original package as umbrella, but in such case we would loose network/ftp name for package with ftp client - any other idea? 2) what to do with SUNWbip legacy tag. SUNWbipr can stay with network/ftp (only etc/default/ftp is there), but SUNWbip deliverables will be in both new packages. - can IPS handle SUNWbip tag in both packages somehow? I do not see much benefit it but I do not know all IPS possibilities. - is it acceptable solution to keep SUNWbipr tag in network/ftp and move SUNWbip tak to network/ping (I believe "Basic IP commands" matches ping binary more than ftp client? What is really expected from this legacy tags? This case is one example, there are more such packages (e.g. snoop and rsh in the same package) which needs cleanup. Best regards, Milan _______________________________________________ on-ips-dev mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
