/[dep]/web/deps/dep9.mdwn
ViewVC logotype

Diff of /web/deps/dep9.mdwn

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 276 by sez, Sun Feb 19 21:17:02 2012 UTC revision 277 by sez, Sun Feb 19 21:40:51 2012 UTC
# Line 176  Meaning of the above listed actions: Line 176  Meaning of the above listed actions:
176  - remove: remove inetd.conf entry and matching shadow fragment  - remove: remove inetd.conf entry and matching shadow fragment
177  - enable: enable inetd.conf entry  - enable: enable inetd.conf entry
178    
179  # Transition of "Depends: update-inetd" packages  # Configuration of new server packages
180    
181  A time-limited transition is not a strict requirement, since reconf-inetd and  Packages that have never used update-inetd must do the following:
 update-inetd can co-exist without problems.  
   
 Server packages that depend on update-inetd can be converted as follows:  
182    
183  * remove any references of update-inetd in post{inst,rm} scripts;  * depend on reconf-inetd
184  * install a reconf-inetd fragment in /usr/share/reconf-inetd, as a regular  * install a reconf-inetd fragment in /usr/share/reconf-inetd, as a regular
185    file (ie. not as a conffile);    file (ie. not as a conffile);
186  * replace the dependency on update-inetd with one on reconf-inetd (but see  
187    notes below)  # Transition of "Depends: update-inetd" packages
188    
189    A time-limited transition is not a strict requirement, since reconf-inetd and
190    update-inetd can co-exist without problems.
191    
192  reconf-inetd will not touch any entries that have not been added by itself,  reconf-inetd will not touch any entries that have not been added by itself,
193  including entries added by update-inetd. Thus, a server package that is meant  including entries added by update-inetd. Thus, a server package that is meant
194  to transition from update-inetd to reconf-inetd, must remove any entries that  to transition from update-inetd to reconf-inetd, must remove any entries that
195  it previously added using update-inetd.  it previously added using update-inetd.
196    
197  Below is an example postinst snippet for an ftp server package that is meant  Server packages that depend on update-inetd can be converted as follows:
198  to be transitioned from update-inetd to reconf-inetd in release 2.0:  
199    0) in the first stable Debian release in which reconf-inetd is used by the
200    package:
201    
202    * depend on both update-inetd and reconf-inetd
203    * install a reconf-inetd fragment in /usr/share/reconf-inetd, as a regular
204      file (ie. not as a conffile);
205    * drop any references to update-inetd in postrm, and modify postinst to remove
206      any inetd.conf entries for that package that were previously added using
207      update-inetd
208    
209    Below is an example postinst snippet for the ftpd-ssl server package (assuming
210    it ships /usr/share/reconf-inetc/ftpd-ssl.xinetd):
211    
212  <pre>  <pre>
213      case $1 in      case $1 in
214          configure)          configure)
215              if dpkg --compare-versions "$2" le 2.0; then              if ! -e /var/lib/reconf-inetd/ftpd-ssl.xinetd; then
216                  if which update-inetd; then                  if which update-inetd; then
217                      update-inetd --remove ftp                      update-inetd --remove ftp
218                  fi                  fi
# Line 209  to be transitioned from update-inetd to Line 221  to be transitioned from update-inetd to
221      esac      esac
222  </pre>  </pre>
223    
224    1) in later stable Debian releases, simply drop update-inetd all together
225    (dependency and postinst snippet)
226    
227  # Requirements for xinetd/reconf-inetd fragments  # Requirements for xinetd/reconf-inetd fragments
228    
229  According to xinetd.conf(5), xinetd fragments must have the following fields:  According to xinetd.conf(5), xinetd fragments must have the following fields:

Legend:
Removed from v.276  
changed lines
  Added in v.277

  ViewVC Help
Powered by ViewVC 1.1.5