[debpool] Re: Parse_Control

[Free Ekanayaka]

|--==> Magnus Holmgren writes:

  MH> What do you think about a more general Parse_Control() function? I mean, on 
  MH> the basic level all control files are alike: RFC 822-style "field-name ':' 
  MH> value", and lines beginning with whitespace are continuation lines. Then 
  MH> there are certain fields that are interpreted in particular ways, but that 
  MH> comes a level up. Would this abstraction case any problem?

  MH> I'm thinking that it can work pretty well having one .package or .source file 
  MH> per source package and arch, but that they need to be read back in for 
  MH> certain information, such as which files exist and which which binaries a 
  MH> given source builds. Therefore I suggest that they be relocated to one place 
  MH> (e.g. the db directory) and that new functions be added, which can parse 
  MH> them.

Do you mean moving .package and .source files out from pool/ into the
db directory? I would second that, I don't like to much those extra
files in poo/ ..

Ciao,

Free