Re: packaging ckermit: lots of questions

2004-01-10 Thread Matt Zimmerman
On Sat, Jan 10, 2004 at 04:45:12PM -0800, Matt Zimmerman wrote: > On Sat, Jan 10, 2004 at 06:59:33AM +, Ian Beckwith wrote: > > > I recently ITA'd ckermit, ("a serial and network communications > > package"). Packaging the latest version raised lots of (hopefully > > non-stupid) questions: >

Re: packaging ckermit: lots of questions

2004-01-10 Thread Matt Zimmerman
On Sat, Jan 10, 2004 at 06:59:33AM +, Ian Beckwith wrote: > I recently ITA'd ckermit, ("a serial and network communications > package"). Packaging the latest version raised lots of (hopefully > non-stupid) questions: Do you realize that ckermit is already packaged in stable/non-free and testi

Re: packaging ckermit: lots of questions

2004-01-10 Thread Matt Zimmerman
On Sat, Jan 10, 2004 at 04:45:12PM -0800, Matt Zimmerman wrote: > On Sat, Jan 10, 2004 at 06:59:33AM +, Ian Beckwith wrote: > > > I recently ITA'd ckermit, ("a serial and network communications > > package"). Packaging the latest version raised lots of (hopefully > > non-stupid) questions: >

Re: packaging ckermit: lots of questions

2004-01-10 Thread Matt Zimmerman
On Sat, Jan 10, 2004 at 06:59:33AM +, Ian Beckwith wrote: > I recently ITA'd ckermit, ("a serial and network communications > package"). Packaging the latest version raised lots of (hopefully > non-stupid) questions: Do you realize that ckermit is already packaged in stable/non-free and testi

Re: packaging ckermit: lots of questions

2004-01-10 Thread Thomas Viehmann
Frank Küster wrote: > Ian Beckwith <[EMAIL PROTECTED]> schrieb: > > >>As ckermit config files are executable via >> >>#!/usr/bin/kermit >> >>upstream suggests shipping with an executable config file and letting >>the user run that if desired. This would mean a config file in >>/usr/bin which is s

Re: packaging ckermit: lots of questions

2004-01-10 Thread Thomas Viehmann
Frank Küster wrote: > Ian Beckwith <[EMAIL PROTECTED]> schrieb: > > >>As ckermit config files are executable via >> >>#!/usr/bin/kermit >> >>upstream suggests shipping with an executable config file and letting >>the user run that if desired. This would mean a config file in >>/usr/bin which is s

Re: packaging ckermit: lots of questions

2004-01-10 Thread Frank Küster
Ian Beckwith <[EMAIL PROTECTED]> schrieb: > > As ckermit config files are executable via > > #!/usr/bin/kermit > > upstream suggests shipping with an executable config file and letting > the user run that if desired. This would mean a config file in > /usr/bin which is sure to violate policy and c

Re: packaging ckermit: lots of questions

2004-01-10 Thread Frank Küster
Ian Beckwith <[EMAIL PROTECTED]> schrieb: > > As ckermit config files are executable via > > #!/usr/bin/kermit > > upstream suggests shipping with an executable config file and letting > the user run that if desired. This would mean a config file in > /usr/bin which is sure to violate policy and c