Marius Gedminas wrote:
> On Tue, Dec 15, 2009 at 07:50:48PM +0100, Cornelius Hald wrote:
>> I think I will use the osso-product-info command as this seems to be the
>> "best" way for me to do it.
>>
>> With the other solutions I have some problems:
>>
>> * /etc/osso_software_version does not exist
On Tue, Dec 15, 2009 at 07:50:48PM +0100, Cornelius Hald wrote:
> I think I will use the osso-product-info command as this seems to be the
> "best" way for me to do it.
>
> With the other solutions I have some problems:
>
> * /etc/osso_software_version does not exist on my N900.
>
> * pkg-config
On Tue, 2009-12-15 at 17:44 +0200, Marius Gedminas wrote:
> On Tue, Dec 15, 2009 at 04:37:23PM +0100, Alberto Garcia wrote:
> > On Tue, Dec 15, 2009 at 12:21:58PM +0100, Cornelius Hald wrote:
> >
> > > While developing inside the SDK I used /etc/maemo_version (which is
> > > provided by the packag
On Tue, Dec 15, 2009 at 04:37:23PM +0100, Alberto Garcia wrote:
> On Tue, Dec 15, 2009 at 12:21:58PM +0100, Cornelius Hald wrote:
>
> > While developing inside the SDK I used /etc/maemo_version (which is
> > provided by the package maemo-version) to alter the runtime behavior
> > of some scripts.
On Tue, Dec 15, 2009 at 12:21:58PM +0100, Cornelius Hald wrote:
> While developing inside the SDK I used /etc/maemo_version (which is
> provided by the package maemo-version) to alter the runtime behavior
> of some scripts.
I think it's simpler to check the version of some installed packages
(usi
There is /etc/osso_software_version but the file is part of some package
that can be uninstalled. Then there is osso-product-info command that
reads it from config partition (where it is stored by flasher) and
prints it.
Why do you need it? Maybe checking specific version of specific
feature/d
