Class layout refactory

[Otavio Salvador]

--==-=-=
Content-Type: multipart/mixed; boundary="=-=-="

--=-=-=

Hello folks,

Well, I was thinking about how should we continue to implement the
code and stoped to think again in class layout.

Currently we have some direct problems with the classes:

 SourcePackage (subclass of Package)
 PackageSource (class to build the PackageList)

Someone have a better name to PackageSource?

The names is not good. I think we should change it.

Well, let us think some about PackageSource classes. They will build a
PackageList and, to me, a more logical way to do it is provide a
Backend like parameter so this can access all needed information to
build the remote and local package lists without problem.

We all think we should processed at this?

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."

--=-=-=--
--==-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFBBabBLqiZQEml+FURApkdAJ9crrDtpiev7exNpUBoRH2cbc5L/ACfS3Or
rVJa4REDNooHsxGvZy/ktVU=
=XgLk
-----END PGP MESSAGE-----
--==-=-=--