Chris Rees wrote:
>> For PackageKit's "app-install", I wanted to list all
>> ports/packages that had a .desktop file (= an "app").
> I may be misunderstanding you here, but you could just:
>
> [ch...@amnesiac]~% echo /usr/ports/*/*/pkg-plist | xargs egrep
> '\.desktop$' | sed 's|/usr/ports/[a-zA
For PackageKit's "app-install", I wanted to list all
ports/packages that had a .desktop file (= an "app").
This ended up in a large number of "false positives",
since there is no list of the contents of each package.
So the brute-force method is to download *all* of them.
For Slackware, which al
Charlie Kester wrote:
> But I expect these two find & greps will detect the majority of filename
> conflicts. Unless someone has a better recommendation, I'll settle for
> less than perfect.
Using a MANIFEST file for packages works, if you have one available.
It's simply a file listing of the co
Hi freebsd ports,
I updated my ruby program called "portlocate"
to use Ferret rather than Xapian like before:
http://www.algonet.se/~afb/freebsd/portlocate.rb
The program works the same as before, but doesn't
need Xapian which was reoccuringly broken (and GPL).
The main part of Ferret is in C bu
Hi freebsd ports,
I updated my ruby program called "portlocate"
to use Ferret rather than Xapian like before:
http://www.algonet.se/~afb/freebsd/portlocate.rb
The program works the same as before, but doesn't
need Xapian which was reoccuringly broken (and GPL).
The main part of Ferret is in C bu
Joe Marcus Clarke wrote:
Didn't post the ports earlier (before this backend backport),
since it was kinda useless to run with the "dummy" backend. :-)
No problem. I did notice some nits in the plist of packagekit. You
should not include blank lines (even to logically segment
sections). If
Joe Marcus Clarke wrote:
Hopefully this will go into PackageKit 0.4.10, for use
while waiting for required PolicyKit/DeviceKit support.
Besides some (unused) differences in API, the backend is
identical to the one in the latest PackageKit (0.5.2).
Feedback appreciated, maintainer didn't respon
I've backported the PackageKit 0.5.x backend to 0.4.x,
and made some ports for it and the GNOME/KDE frontends.
As described earlier, it uses portupgrade and portaudit
and compiles binary packages from source ports if needed.
http://afb.users.sourceforge.net/packagekit/
Hopefully this will go i
Hi all,
I have made a "ports" backend for PackageKit (http://packagekit.org/)
that uses ports-mgmt/portupgrade and optionally ports-mgmt/portaudit.
It's a spawned backend, which means that the dbus deamon will start
a Ruby script that then dispatches command for as long as it runs...
It's curr
