[Catalog-sig] "implementation" of PEP 262 as an academic project

[Richard Jones]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 30 Apr 2005 02:56 pm, Maurice LING wrote:
> > I've just read PEP 262 last night and finds that it does more or less
> > describes what I have in mind. However, I am not sure if there is every
> > need for such a descriptive database file or something slimmer, like
> > Fink's .info files will suffice.

You should make yourself familiar with the latest metadata PEP 314 (specifies 
metadata version 1.1). I'm also currently working on metadata version 1.2, 
which allows specification of python version requirements, and external 
software requirements.


> > Implementing the API specified in PEP 262 is desirable.
> >
> > What I am thinking is this,
> >
> > 1. when user specify a package to install, the package's .info file will
> > be looked up in 'pkginfo' directory (in PEP 262, it is the INSTALLDB
> > directory that holds all these .info files).
> >
> > 2. to the system, only 3 things are crucial: where to get the package?
> > what packages the package needs? how to install? These 3 things are the
> > real critical parts of .info file, the rest are information and metadata.

You might need to prompt the user for handling external dependencies here.
 

> > Please tell me what you think...

Sounds good to me. I'd like to see the PEP (261) updated with the latest state 
of distutils (ie. metadata, the package index), your ideas and re-posted.


    Richard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCdVtqrGisBEHG6TARAsxFAJ9906N9GwODpcoNqEcNqXi37tcKiwCeMNu3
5dmJVm97e8ZrsjxHwAcbwnM=
=hhwI
-----END PGP SIGNATURE-----