> On Wed, 2006-05-24 at 11:40 +0200, Simon Matter wrote: >> While trying to build updated rpms of 2.3.4 I found the lmtpproxyd is >> now >> created as a hardlink to lmtpd. The same applies to pop3proxyd which is >> linked to pop3d. In the past the rpm shipped without the hardlinked >> pop3proxyd because it was not really used. My question is now what is >> the >> correct way to handle those links. Is there a good reason to include >> them >> in the package or are they just there for those using old config files? > > As of 2.3.3 proxy functionality was incorporated into daemons. > As of 2.3.3 you don't need separate frontends and backends - > same daemon can serve or proxy depend whether it has mailbox locally > or not. I understand that, however lmtpproxyd didn't exist in 2.3.x until 2.3.4. It was there in 2.2 but not in 2.3 until now. Why did they appear now, did nobody need them in 2.3.3? So my question is, do those binaries act different depending on how they were called? If that's the case then the rpms should also ship with the hardlinked files. Simon ---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
