Subversion Repositories

?revision_form?Rev ?revision_input??revision_submit??revision_endform?

Rev 1 | Only display areas with differences | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 1 Rev 5
1
Why have yet another Debian package repository tool?
1
Why have yet another Debian package repository tool?
2
2
3
* Most or all of the other tools require extensive non-core support.
3
* Most or all of the other tools require extensive non-core support.
4
4
5
  While many users may not find this problematic, those working on a new
5
  While many users may not find this problematic, those working on a new
6
  port, and trying to make it self-hosting, will often have a difficult
6
  port, and trying to make it self-hosting, will often have a difficult
7
  time trying to get some of the more packages with a complex tree of
7
  time trying to get some of the more packages with a complex tree of
8
  Build-Dependancies (such as Python) to a point where they can be
8
  Build-Dependancies (such as Python) to a point where they can be
9
  compiled. Conversely, a working shell, an installation of Perl, and
9
  compiled. Conversely, a working shell, an installation of Perl, and
10
  a compiler are some of the first things that must be present, simply
10
  a compiler are some of the first things that must be present, simply
11
  because so much of the rest of the system depends on these (and they are
11
  because so much of the rest of the system depends on these (and they are
12
  often available from another port or a non-Debian system).
12
  often available from another port or a non-Debian system).
13
13
14
  Therefore, I have attempted to keep the requirements for packages not
14
  Therefore, I have attempted to keep the requirements for packages not
15
  found in the Debian core system (Essential packages, or those with
15
  found in the Debian core system (Essential packages, or those with
16
  Priority required) to an absolute minimum (ideally, 'none'), or at the
16
  Priority required) to an absolute minimum (ideally, 'none'), or at the
17
  very least, only require packages that can easily be compiled on a system
17
  very least, only require packages that can easily be compiled on a system
18
  with little more than a shell, perl, and a working C compiler.
18
  with little more than a shell, perl, and a working C compiler.
19
19
20
  Note that some amount of significant functionality (such as Release
20
  Note that some amount of significant functionality (such as Release
21
  files and signature checking) does depend on more complex packages (such
21
  files and signature checking) does depend on more complex packages (such
22
  as GnuPG or the perl Digest modules), which is why these are in the
22
  as GnuPG or the perl Digest modules), which is why these are in the
23
  Recommends field; however, these functions that use these are niceties
23
  Recommends field; however, these functions that use these are niceties
24
  (if very useful ones), and an archive can operate without them, if
24
  (if very useful ones), and an archive can operate without them, if
25
  necessary.
25
  necessary.
26
26
27
* No other tool handles the new pool-style layout readily.
27
* No other tool handles the new pool-style layout readily.
28
28
29
  As of this writing, none of the tools in Debian except for katie (part
29
  As of this writing, none of the tools in Debian except for katie (part
30
  of the softare used to run the primary Debian archives) can handle a
30
  of the softare used to run the primary Debian archives) can handle a
31
  pool-style directory layout in any straightforward fashion, while setting
31
  pool-style directory layout in any straightforward fashion, while setting
32
  up a full instance of katie requires significant support infrastructure
32
  up a full instance of katie requires significant support infrastructure
33
  (such as an SQL server, among other things).
33
  (such as an SQL server, among other things).