Re: Inital Deb Filter

["Kevin Kubasik" <kevin kubasik net>]

Ok, I started fixing FilterDeb to use FilterPackage, but a few questions.

1) Do we not want to index any dependency information at all? ATM I
was planning on leaving in the code in the deb filter that extracted
and stored all the dependencies, which might be a nice UI
feature/something that someone who writes a 'Package Backend' would
need.

2) Are we making the description a property or the text. In the debian
world, the Description of a package is 2-6 paragraphs detailing the
packages function. Which seems much more like something we should
treat as text (ie AppendText()) as opposed to a huge property.
Especially since debian package descriptions can be very long, we
would want to have the option of snippeting the descriptions, not
displaying the whole thing in the UI. (Hence why I have SnippetMode =
true).

3) ATM the FilterPackage class includes some information that Debian
archives do not include (ie license and homepage being the primary
culprits) Those fields can be left blank, but since the information is
not available in all packages, shouldn't it be just in the FilterRPM
class?

Just my $0.02, lemme know how I should proceed,
Kevin Kubasik
On 4/22/06, Kevin Kubasik <kevin kubasik net> wrote:
> Ok, I'll probably get around to that Sunday afternoon, looks easy enough.
>
> -Kevin K
>
> On 4/21/06, D Bera <dbera web gmail com> wrote:
> > On Friday 21 April 2006 18:10, Pat Double wrote:
> > > On Friday 21 April 2006 17:02, D Bera wrote:
> > > > Pat, I changed FilterEbuild to derive from FilterPackage. Nothing should
> > > > be broken since I didnt change any functionality and I tested it on 2
> > > > simple ebuilds. But you might want to go through it once to make sure I
> > > > didnt drop anything in copy/paste. I dont know the ebuild format good
> > > > enough.
> > > >
> > > > - dBera
> > >
> > > Will do. I don't know if the Deb and RPM filters put in installation info
> > > into the properties, but if so I also have a patch to the ebuild filter to
> > > do so. It would be nice to standarize on those properties like the size of
> > > the installed files, when it was installed, etc.
> >
> > For RPM, I try to extract the information that is useful for searching or
> > displaying. I didnt feel filesizes would be useful to extract so I didnt. Its
> > upto you for the ebuild filter. But since filesizes can be only be extracted
> > from "installed"-ebuilds and not ebuilds lying in the file-system, and I am
> > not sure how can it be used while displaying in beagle-search, I am not too
> > keen on adding that information to FilterPackage. Just add them specific to
> > FilterEbuild.
> >
> > - dBera
> >
> > --
> > --------------------------------------------------------
> > Debajyoti Bera @ http://dbera.blogspot.com
> > beagle / KDE fan
> > Mandriva / Inspiron-1100 user
> > _______________________________________________
> > Dashboard-hackers mailing list
> > Dashboard-hackers gnome org
> > http://mail.gnome.org/mailman/listinfo/dashboard-hackers
> >
>
>
> --
> Cheers,
> Kevin Kubasik
> http://blog.kubasik.net/
>


--
Cheers,
Kevin Kubasik
http://blog.kubasik.net/