File: README

package info (click to toggle)
searchscripts 0.11
  • links: PTS
  • area: main
  • in suites: woody
  • size: 224 kB
  • ctags: 3
  • sloc: makefile: 34
file content (151 lines) | stat: -rw-r--r-- 4,480 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151

I rarely use a couple of these scripts.  If you do and you see
a problem please file a bug or email me or it will probably go
unnoticed.

lynx is the recommended browser for the scripts.  The output
can sometimes look  crappy in other browsers.  If lynx isn't
your normal default you can set it for just these scripts with
the SSBROWSER environment variable.


searchgeo

    Geocrawler archives many Debian lists.  It's often faster than
    lists.debian.org.

diffdirs

    using with FileRunner
    ---------------------
    I have the following in FileRunner's config file so that
    diffdirs is called with the Diff button:

        set config(cmd,diff) {dodiff {%s} {%s}}

    dodiff is this shell script:

        #!/bin/sh
        DIFFDIRS=tkdiff diffdirs -s "$@"
        exit 1

    The non-zero exit makes FileRunner put the result in its error
    window.  This is a little messy but seems the best way to go
    without hacking FileRunner.

    using with Worker (a DirOpus-style directory utility)
    -----------------
    'in terminal'
    diffdirs {uF} {ouF} |less

ppack

    -D|R
    ----
    The -D and -R options showing the depends/reverse depends
    trees are a gimmick really.  -D uses "apt-cache depends"
    output and if there are alternatives, takes the last one.
    Also if it depends on a virtual package, just the virtual
    package name is printed rather than picking a package that
    provides it.

    For example, debhelper:

          debhelper's Depends line:
            Depends: perl5 | perl (>= 5.004), fileutils (>= 4.0-2.1), \
                         file (>= 3.23-1), dpkg-dev (>= 1.7.0), lynx

          $ apt-cache depends debhelper
             |Depends: <perl5>
                perl-5.005
                perl-5.6
                perl-5.004
              Depends: perl
              Depends: fileutils
              Depends: file
              Depends: dpkg-dev
              Depends: lynx
                lynx-ssl

          $ ppack -D debhelper 1
             |- dpkg-dev
             |- file
             |- fileutils
             |- lynx
             |- perl

    It was easy to implement this way and it's not clear if much
    is gained by following the first alternative instead, or by
    following all alternatives, which would be easy to do as
    well.  The same for picking a package that provides for the
    virtual package instead of just printing the virtual package
    name.

    If you've installed a package since your last update, this
    will run about 5x faster if you "apt-get update" first.

    -ch
    ---
    This compares the package names in the current Packages files in
    /var/state/apt/lists against a list of packages from the previous
    Packages files for a distribution, showing which packages were
    added and removed.

    This is probably most useful when run once a day after root
    runs "apt-get update".

    "ppack -P '?'" gives an explanation of selecting patterns to key
    on different distros.  Assuming you track unstable, the APT-0.4
    packages at klecker.debian.org/~jgg, testing & progeny this
    wrapper would work,

            #!/bin/sh
            for i in unstable testing jgg progeny _stable
            do
                /usr/bin/ppack -ch $i
            done

    The save names (in ~/.changed-pkgs/) are created from the
    arguments so you'll want to pick unique strings for the
    Packages files you want to track and stick with them.


APT
---
  ppack is most useful with APT >= 0.4.  This APT allows you
  to pin distributions / releases so that you can have their
  Packages files but not have to worry about having an unwanted
  package installed during upgrade.  If you run testing the
  following would allow you to track unstable as well:

  /etc/apt/sources.list
  ---------------------
  deb http://http.us.debian.org/debian unstable main contrib non-free
  deb http://http.us.debian.org/debian testing main contrib non-free

  /etc/apt/preferences
  --------------------
    Package: *
    Pin: release a=testing
    Pin-Priority: 998

    Package: *
    Pin: release a=unstable
    Pin-Priority: -1

  You'll want to set PPDIST='unstable apt' or so and override that
  on the command line when desired.

  You can see what's newer than your installed testing versions with
    ppack -u unstable

  And this would install deborphan from unstable:
    apt-get install deborphan/unstable



Rick Younie <younie@debian.org>
Oct 2001


vim:et