<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel">
    <title>gmane.comp.package-management.opkg.devel</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/391"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/389"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/388"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/387"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/386"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/386"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/385"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/384"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/383"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/382"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/381"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/380"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/379"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/378"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/377"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/376"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/375"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/374"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/373"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/372"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/391">
    <title>[RFC] Add basic OpenSSL CLR check support</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/391</link>
    <description>&lt;pre&gt;Hi all,
the attached patch adds a basic crl check mechanism.

The reason to suggest jet another crl check mechanism is that, as far as I know, the current crl check "libpathfinder" requires dbus and I want to build a basic distribution without it. Without libpathfinder there is no way to revoke certificates.

What does the patch do? It will do the same as the openssl tool smime verify -crl_check or -crl_check_all does. It sets the verify option according to the added opkg config options (crl_check and crl_check_all). crl_check checks only one authority and crl_check_all checks the whole path. The verify function checks the crl's included at the X509_STORE object at every verify operation. Therefore the crl must be included either at the ca_signature_path or ca_signature_file. The default value of crl_check and crl_check_all is false, so there is no behaviour change if one does not change the opkg.config on an update. Also it does not disturb the libpathfinder mechanism. This is the reason why it is not escap&lt;/pre&gt;</description>
    <dc:creator>Bernhard Guillon</dc:creator>
    <dc:date>2013-04-04T12:34:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/389">
    <title>Working around Beaglebone opkg upgrade bug</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/389</link>
    <description>&lt;pre&gt;I posted a problem on the Angstrom-users list but have had no replies.
Perhaps the list is inactive:
http://lists.linuxtogo.org/pipermail/angstrom-distro-users/2012-October/004118.html

Basically running "opkg update &amp;amp;&amp;amp; opkg upgrade" on the beagleBONE
doesn't work. It appears to break various //var/lib/opkg/info/*.list
files.

As a result to keep internet facing services up to date I had to do a
work-around with "opkg --force-reinstall install openssh". With this
you have to get the exact package match; "opkg --force-reinstall
install ssh" doesn't work.

The force reinstall will download the latest package according to any
changes resulting from "opkg update".

I hope this helps someone.

If you are running dropbear you'll get a conflict. I don't know how to
do this change from dropbear to openssh without losing remote
connectivity. Running a screen session might work but if the
changeover fails you might end up reimaging the sdcard image to the
sdcard. Might be better to stick with dropbear until you come a&lt;/pre&gt;</description>
    <dc:creator>jago25</dc:creator>
    <dc:date>2012-10-31T12:38:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/388">
    <title>opkg list issue</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/388</link>
    <description>&lt;pre&gt;Hi,

I am trying to create a local opkg repository. I have created sample debian 
package and renamed final package to .opk.
I have opkg.conf file at /etc/opkg, in which I specified my local 
repository directory as 

src/gz packages file:///root/packages

when I try running "*opkg-cl list*", it comes out without any list details. 
On running in verbose mode I see this

opkg_conf_parse_file: Loading conf file /etc/opkg/opkg.conf.
pkg_hash_load_feeds: 
pkg_hash_load_status_files: 
hash_table: pkg-hash, 12288 bytes
n_buckets=1024, n_elements=0, n_collisions=0
max_bucket_len=0, n_used_buckets=0, ave_bucket_len=0.00
n_hits=0, n_misses=0
hash_table: file-hash, 12288 bytes
n_buckets=1024, n_elements=0, n_collisions=0
max_bucket_len=0, n_used_buckets=0, ave_bucket_len=0.00
n_hits=0, n_misses=0
hash_table: obs-file-hash, 768 bytes
n_buckets=64, n_elements=0, n_collisions=0
max_bucket_len=0, n_used_buckets=0, ave_bucket_len=0.00
n_hits=0, n_misses=0


I am not sure why its not able to fetch the package. Please can so&lt;/pre&gt;</description>
    <dc:creator>Manjunath G</dc:creator>
    <dc:date>2012-10-04T20:22:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/387">
    <title>opkg list issue</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/387</link>
    <description>&lt;pre&gt;Hi,

I am trying to setup a local opkg repository. I have created the sample 
package. I have followed the steps for creating debian package and then 
renamed final package to .opk. 
I have a opkg.conf file in /etc/opkg directory, where I specified my local 
directory like this

src/gz packages file:///root/packages

But when I try "opkg-cl list", it just comes out without any output. 

When I try running in verbose mode I see 

opkg_conf_parse_file: Loading conf file /etc/opkg/opkg.conf.
pkg_hash_load_feeds: 
pkg_hash_load_status_files: 
hash_table: pkg-hash, 12288 bytes
n_buckets=1024, n_elements=0, n_collisions=0
max_bucket_len=0, n_used_buckets=0, ave_bucket_len=0.00
n_hits=0, n_misses=0
hash_table: file-hash, 12288 bytes
n_buckets=1024, n_elements=0, n_collisions=0
max_bucket_len=0, n_used_buckets=0, ave_bucket_len=0.00
n_hits=0, n_misses=0
hash_table: obs-file-hash, 768 bytes
n_buckets=64, n_elements=0, n_collisions=0
max_bucket_len=0, n_used_buckets=0, ave_bucket_len=0.00
n_hits=0, n_misses=0

I am no&lt;/pre&gt;</description>
    <dc:creator>Manjunath G</dc:creator>
    <dc:date>2012-10-04T20:11:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/386">
    <title>Behaviour of -f</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/386</link>
    <description>&lt;pre&gt;

Hi all,

I've noticed recently that the -f option, which specifies an alternative
configuration file, does not cause opkg to ignore configuration files in
/etc/opkg - these are apparently always read. Is this desirable behaviour?
It's certainly inconvenient within an OpenEmbedded context - after we
install the default config file into ${ROOTFS}/etc/opkg, opkg can start
behaving differently due to the altered configuration.

Cheers,
Paul

-----
Paul Eggleton
Intel Open Source Technology Centre

&lt;/pre&gt;</description>
    <dc:creator>Paul Eggleton</dc:creator>
    <dc:date>2012-07-05T10:13:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/386">
    <title>Behaviour of -f</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/386</link>
    <description>&lt;pre&gt;

Hi all,

I've noticed recently that the -f option, which specifies an alternative
configuration file, does not cause opkg to ignore configuration files in
/etc/opkg - these are apparently always read. Is this desirable behaviour?
It's certainly inconvenient within an OpenEmbedded context - after we
install the default config file into ${ROOTFS}/etc/opkg, opkg can start
behaving differently due to the altered configuration.

Cheers,
Paul

-----
Paul Eggleton
Intel Open Source Technology Centre

&lt;/pre&gt;</description>
    <dc:creator>Paul Eggleton</dc:creator>
    <dc:date>2012-07-05T10:13:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/385">
    <title>Re: Re: OPKG Repository Server Setup</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/385</link>
    <description>&lt;pre&gt;
newer version is here
http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/
for python-2.6 you need last patch from:
https://github.com/shr-project/opkg-utils/tree/jansa/pull
until it's merged to yoctoproject repo.


and use -r option when regenerating index (won't parse all .ipk files,
just new and changed).


yes

Cheers,


&lt;/pre&gt;</description>
    <dc:creator>Martin Jansa</dc:creator>
    <dc:date>2012-06-05T10:20:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/384">
    <title>Re: OPKG Repository Server Setup</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/384</link>
    <description>&lt;pre&gt;I see. No Replys. Found it myself.

For anyone else having the same question:

An OPKG Repository is just a simple HTTP Servier with a special file
structure.
Setup:
1. Checkout the opkg-utils from http://svn.openmoko.org/trunk/src/host/opkg-utils/
(svn checkout http://svn.openmoko.org/trunk/src/host/opkg-utils/)
2. make &amp;amp;&amp;amp; make install
3. run "opkg-make-index" to add Packages to your Repository.
4. For a full featured opkg-repository you will need the Paketindex -
you can create one with
"gzip -c Packages &amp;gt; Packages.gz"
5. Copy files to your http server of your choice - add URL to your
"myrepo.conf" in /etc/opgk folder.



Correct?

Thanx for the help.

(like doing conversations with myself)


Anyone has a clue (or a guideline) how to secure a repository to
unauthorized access?

On 1 Jun., 14:35, HenningS &amp;lt;h.spi...-gM/Ye1E23mwN+BqQ9rBEUg&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>HenningS</dc:creator>
    <dc:date>2012-06-05T09:56:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/383">
    <title>OPKG Repository Server Setup</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/383</link>
    <description>&lt;pre&gt;Hi Group,

im searching for information for setting up an repository for OPKG
pakages.
I could not find anything in this group (and in the internet surely) -
which i hope is mostly related to this topic.
Can someone give me some hints?

Would an OPKG repository be the same like an IPKG Repo?

Regards,

Henning

&lt;/pre&gt;</description>
    <dc:creator>HenningS</dc:creator>
    <dc:date>2012-06-01T12:35:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/382">
    <title>Adding layers</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/382</link>
    <description>&lt;pre&gt;Hi,

I know this is probably more the place for code level discussion and
bug fixes, but i'm hitting a brick wall finding good documentation on
OEs directory structure and the steps involved in adding layers on top
of OE-core. So apologies in advance.

I'm trying to migrate from OE-dev to OE-core. From installing the oe-
made-easy package, in oe-core i have:
bitbake  build  BUILD-qemux86-64  LICENSE  meta  meta-hob  meta-
skeleton  oe-init-build-env  README  scripts

I see there are a number of meta layers available. So say i wanted to
add support for angstrom, where do i put meta-angstrom? and how do i
specify i want to build an angstrom distro?

Thanks.

&lt;/pre&gt;</description>
    <dc:creator>Meister Murphy</dc:creator>
    <dc:date>2012-05-24T08:36:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/381">
    <title>Re: opkg equivalent of /var/lib/dpkg/info/ ?</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/381</link>
    <description>&lt;pre&gt;Hi,

It's ok, i found it shortly after posting.

configure with --with-opkglibdir=/path/

But you need to make sure /path/ has an opkg subdir.

Thanks.

On May 24, 9:00 am, akostop &amp;lt;akosto...-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Meister Murphy</dc:creator>
    <dc:date>2012-05-24T07:31:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/380">
    <title>Re: opkg equivalent of /var/lib/dpkg/info/ ?</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/380</link>
    <description>&lt;pre&gt;In my installation at least (i don't remember how i configured it),
metadata are in /usr/lib/opkg/. Yours will be, obviously, in /usr/
local/lib/opkg

On May 23, 7:33 pm, Meister Murphy &amp;lt;meister.mur...-gM/Ye1E23mwN+BqQ9rBEUg&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
wrote:

&lt;/pre&gt;</description>
    <dc:creator>akostop</dc:creator>
    <dc:date>2012-05-24T07:00:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/379">
    <title>opkg equivalent of /var/lib/dpkg/info/ ?</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/379</link>
    <description>&lt;pre&gt;Hi all,

I'm trying to reconfigure opkg so that all the meta data on its
installed packages are where i want them to be.
I see the pkgdatadir is /usr/local/share/opkg by default, but in there
all i see is:

/usr/local/share/opkg/intercept:
depmod  ldconfig  update-modules

Can someone throw some light on this?

Cheers.

&lt;/pre&gt;</description>
    <dc:creator>Meister Murphy</dc:creator>
    <dc:date>2012-05-23T16:33:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/378">
    <title>Re: Re: How to make a package...</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/378</link>
    <description>&lt;pre&gt;Thanks, i will try.

On 05/21/2012 10:39 AM, akostop wrote:


&lt;/pre&gt;</description>
    <dc:creator>Thanat0s</dc:creator>
    <dc:date>2012-05-21T18:23:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/377">
    <title>Re: How to make a package...</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/377</link>
    <description>&lt;pre&gt;Since opkg packages are actually deb packages, you could see any
tutorial on making .deb packages (there are lots of them out there).
You could use dpkg-buildpackage, svn-buildpackage, build them manually
etc. You can them rename them to .opkg (or not; we're using .deb
packages with opkg, it works just fine)

On May 21, 8:54 am, Thanat0s &amp;lt;thans...-hq31Uk0SuEaWVfeAwA7xHQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>akostop</dc:creator>
    <dc:date>2012-05-21T08:39:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/376">
    <title>How to make a package...</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/376</link>
    <description>&lt;pre&gt;Hi all, i had successfully compiled (... Victory !!) the last bacula
on my system (arm gnap nas), how could i do a package for other
people ?, the wiki says ...

You can learn how to create own Opkg packages &amp;lt;http://handhelds.org/
moin/moin.cgi/BuildingIpkgs&amp;gt; on the Ipkg site.

But the links is dead.. i need a tuto, i never done a ipkg.

Bye.

&lt;/pre&gt;</description>
    <dc:creator>Thanat0s</dc:creator>
    <dc:date>2012-05-21T05:54:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/375">
    <title>install multi packages using '*'</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/375</link>
    <description>&lt;pre&gt;Hey, I want to install a few packages 'coreutils'. There is a lot of
packages named 'coreutils-[util name]'.
When I try to install them all using 'opkg install coreutils-*', I get
this:

Unknown package 'coreutils-*'.
Collected errors:
 * opkg_install_cmd: Cannot install package coreutils-*.

Is there any options to install them all at once?

Best regards, Jacek.

&lt;/pre&gt;</description>
    <dc:creator>Jacek Łacny</dc:creator>
    <dc:date>2012-05-02T15:07:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/374">
    <title>opkg relinks symlinks during unpack to the wrong file</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/374</link>
    <description>&lt;pre&gt;Hi,

I've been trying to debug a weird failure in my 3d driver which turned
out to be an opkg bug.

Files after build, before making an .ipk out of them:

koen&amp;lt; at &amp;gt;dominion:/OE/tentacle/build/tmp-angstrom_2010_x-eglibc/work/
armv7a-angstrom-linux-gnueabi/libgles-omap3-4.05.00.03-r29/image/usr/
lib$ ls -la | grep libsrv_um
lrwxrwxrwx 1 koen koen      28 2012-05-02 11:28 libsrv_um_dri.so -&amp;gt;
libsrv_um_dri.so.1.6.16.4117*
lrwxrwxrwx 1 koen koen      28 2012-05-02 11:28 libsrv_um_dri.so.1 -&amp;gt;
libsrv_um_dri.so.1.6.16.4117*
lrwxrwxrwx 1 koen koen      28 2012-05-02 11:28 libsrv_um_dri.so.1.6 -
-rwxr-xr-x 1 koen koen  647704 2011-10-11 13:36 libsrv_um_dri.so.
1.6.16.4117*
lrwxrwxrwx 1 koen koen      24 2012-05-02 11:28 libsrv_um.so -&amp;gt;
libsrv_um.so.1.6.16.4117*
lrwxrwxrwx 1 koen koen      24 2012-05-02 11:28 libsrv_um.so.1 -&amp;gt;
libsrv_um.so.1.6.16.4117*
lrwxrwxrwx 1 koen koen      24 2012-05-02 11:28 libsrv_um.so.1.6 -&amp;gt;
libsrv_um.so.1.6.16.4117*
-rwxr-xr-x 1 koen koen  647307 2011-10-12 13:09 libsrv_um.so.
1.6.16.4117*

Obs&lt;/pre&gt;</description>
    <dc:creator>Koen Kooi</dc:creator>
    <dc:date>2012-05-02T10:26:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/373">
    <title>Re: upgrade loses auto-installed flag</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/373</link>
    <description>&lt;pre&gt;

I commited a slightly modified version of your patch, and a fix :-)

&lt;/pre&gt;</description>
    <dc:creator>Camille Moncelier</dc:creator>
    <dc:date>2012-01-19T14:04:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/372">
    <title>upgrade loses auto-installed flag</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/372</link>
    <description>&lt;pre&gt;Hi all,

when upgrading a package that was auto-installed as a dependency it loses the
"Auto-installed: yes" flag. Therefore it will not be automatically removed
once it becomes orphaned.

The attached test case illustrates the behavior.

Regards,
Christian

&lt;/pre&gt;</description>
    <dc:creator>Christian Hitz</dc:creator>
    <dc:date>2011-12-21T13:23:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/371">
    <title>Opkg patches and bugs in OE-core</title>
    <link>http://permalink.gmane.org/gmane.comp.package-management.opkg.devel/371</link>
    <description>&lt;pre&gt;Hi,

I case you haven't read it: http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014496.html

regards,

Koen

&lt;/pre&gt;</description>
    <dc:creator>Koen Kooi</dc:creator>
    <dc:date>2011-12-16T07:25:57</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.package-management.opkg.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.package-management.opkg.devel</link>
  </textinput>
</rdf:RDF>
