Requires(missingok)
by Jason L Tibbitts III
I saw a review ticket for a package which uses Requires(missingok):
which I have not seen before. Some searching turned up the kismet and
python-docutils which currently use this idiom.
What is this actually supposed to do? I can understand what
Requires(hint) might do, but Requires(missingok) sounds more like it
wouldn't actually do anything if the dependency is not present, which
would make me wonder as to the point of having it at all.
Do we want Requires(missingok) in Fedora packages?
- J<
16 years, 1 month
Packaging J2ME java midlets for Fedora. Is it possible ?
by Mike F
Hi all
I was wondering if I should package J2ME java midlet for Fedora.
In general, J2ME midlets is java software which should be uploaded to cell phone to work.
Instead of ordinary J2SE java software J2ME midlet can not be compiled with IcedTea of Sun JDK only.
It need to installSun WTK or toolkits from other vendors (Nikia, Motorola...) in addition to do that.
These toolkits are free downloadable, but are not open source.
So, is it ever possible to package J2ME midlet for Fedora ?
Thanks
Mikhail
16 years, 1 month
packaging ramspeed, which uses the "The Alasir Licence" (TAL)
by Thorsten Leemhuis
Hi Spot, all
I was wondering if I should package ramspeed,
http://www.alasir.com/software/ramspeed/
for Fedora. But It uses a odd license -- "The Alasir Licence" (TAL)
http://www.alasir.com/licence/TAL.txt
I couldn't find it on
http://fedoraproject.org/wiki/Licensing#SoftwareLicenses
See below for the text. What do you guys think, is it acceptable for Fedora?
Is the "the software (the whole or a part of it) is prohibited from being sold or
leased in any form or manner with the only possible exceptions: [...]" part a
problem?
Cu
knurd
---
The Alasir Licence
This is a free software. It's provided as-is and carries absolutely no
warranty or responsibility by the author and the contributors, neither in
general nor in particular. No matter if this software is able or unable to
cause any damage to your or third party's computer hardware, software, or any
other asset available, neither the author nor a separate contributor may be
found liable for any harm or its consequences resulting from either proper or
improper use of the software, even if advised of the possibility of certain
injury as such and so forth.
The software isn't a public domain, it's a copyrighted one. In no event
shall the author's or a separate contributor's copyright be denied or violated
otherwise. No copyright may be removed unless together with the code
contributed to the software by a holder of the respective copyright. A
copyright itself indicates the rights of ownership over the code contributed.
Back and forth, the author is defined as the one who holds the oldest
copyright over the software. Furthermore, the software is defined as either
source or binary computer code, which is organised in the form of a single
computer file usually.
The software (the whole or a part of it) is prohibited from being sold or
leased in any form or manner with the only possible exceptions:
a) money may be charged for a physical medium used to transfer the software;
b) money may be charged for optional warranty or support services related to
the software.
Nevertheless, if the software (the whole or a part of it) is desired to
become an object of sale or lease (the whole or a part of it), then a separate
non-exclusive licence agreement must be negotiated from the author. Benefits
accrued should be distributed between the contributors or likewise at the
author's option.
Whenever and wherever the software is distributed, in either source or
binary form, either in whole or in part, it must include the complete
unchanged text of this licence agreement unless different conditions have been
negotiated. In case of a binary-only distribution, the names of the copyright
holders must be mentioned in the documentation supplied with the software.
This is supposed to protect rights and freedom of those who have contributed
their time and labour to free software development, because otherwise the
development itself and this licence agreement are of a very little sense.
Nothing else but this licence agreement grants you rights to use, modify
and distribute the software. Any violation of this licence agreement is
recognised as an action prohibited by an applicable legislation.
16 years, 1 month
how to handle mimetype
by Eric Tanguy
I'm trying to package scidavis http://scidavis.sourceforge.net/ and i
would like the files generated by it (*.sciprj and *.sciprj.gz) will be
associated to scidavis and opened in it when i double-click on their.
So i put a desktop file in /usr/share/applications :
[Desktop Entry]
Encoding=UTF-8
Name=SciDAVis
Comment=Scientific Data Analysis and Visualization
Comment[de]=Visualisierungs- und Datenanalyseprogramm
Comment[fr]=Outil d'analyse scientifique de données
Icon=scidavis
Exec=scidavis %f
Terminal=0
Type=Application
Categories=Science;Graphics;X-Fedora;
MimeType=application/x-scidavis
X-Desktop-File-Install-Version=0.13
and a xml file in /usr/share/mime/packages :
<?xml version="1.0" encoding="UTF-8"?>
<mime-info
xmlns="http://www.freedesktop.org/standards/shared-mime-info">
<mime-type type="application/x-scidavis">
<comment>Scidavis project</comment>
<glob pattern="*.sciprj"/>
</mime-type>
<mime-type type="application/x-scidavis">
<comment>Scidavis project</comment>
<glob pattern="*.sciprj.gz"/>
</mime-type>
</mime-info>
after this i run
update-mime-database /usr/share/mime
update-desktop-database
but the problem is that when i create a sciprj file using scidavis the
mime-type associated in nautilus is text/html
Someone could help me to clarify this ?
Thanks
Eric
16 years, 1 month
%bits macro?
by Orion Poplawski
It might me useful to have a %bits macro automatically set to 32 or 64
as appropriate. Does this seem useful or is there a better way?
I'm try to follow the following tip from
http://fedoraproject.org/wiki/PackagingDrafts/MultilibTricks:
#if __WORDSIZE == 32
#include "myautoconfig-32.h"
#elif __WORDSIZE == 64
#include "myautoconfig-64.h"
#else
#error "Unknown word size"
#endif
So in my spec I want to move "myautoconfig.h" to "myautoconfig-32.h" (or
64) as appropriate. Would be nice to do:
mv myautoconfig.h myautoconfig-%{bits}.h
Thoughts?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
16 years, 1 month
