patch: obexftp portability fix

Hi Christian,

here's a small portability fix for obexftp that allows compilation on OS 
X.

Alexander

Homepage: http://www.sensi.org/~ak/

diff -uNr obexftp-0.19/obexftp/cache.c obexftp-0.19.new/obexftp/cache.c
--- obexftp-0.19/obexftp/cache.c	2006-01-11 19:09:25.000000000 +0200
+++ obexftp-0.19.new/obexftp/cache.c	2006-05-01 19:48:35.000000000 +0300
 <at>  <at>  -286,14 +286,14  <at>  <at> 
 		if (h) sscanf (h, "size=\"%200[^\"]\"", size);
 	
 		if (!strcmp("folder", tagname)) {
-                        dir->mode = __S_IFDIR | 0755;
+                        dir->mode = S_IFDIR | 0755;
                         strcpy(dir->name, name);
 			dir->mtime = atotime(mod);
                         dir->size = 0;
 			dir++;
                 }
 		if (!strcmp("file", tagname)) {
-                        dir->mode = __S_IFREG | 0644;
+                        dir->mode = S_IFREG | 0644;
                         strcpy(dir->name, name);
 			dir->mtime = atotime(mod);
 			i = 0;

HP CapShare Support?

I dug out my old CapShare again to see if I could figure out how to make it work.  All the obenobex web sites list
it as supported but I don't know exactly how to receive files from it.  I tried obex_test and get nothing.  I
know my IRDA is working because irdadump lists data coming from i.  I'm confused as to where to go from here. 
Anyone got one working before?
t


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642

openobex patches from Debian

Hi,

I am the current openobex maintainer for Debian and have collected some 
patches, mainly for the apps in the package:

* docbuild.patch makes creation of the documentation possible again

* ircp.patch fixes some security related problems (although low risk, it is 
still valid) that would overwrite files in receive mode. Instead, it adds a 
random string to the file (using mkstemp).

* obex_test.patch adds some error checking to the code and adds some missing 
ifs for the default case

* rodrigues_irobex_palm3.patch adds the possibility to specify the creation-ID 
of the object to send

I also have manpages for all apps in the package. If you are interested (they 
are written in docbook), please tell me (I have to rip out some sentences 
about Debian, first).

There are other bug reports in line waiting for a fix:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libopenobex

One issue with the IrDA-Server-Code (see debian bugs #236371 and #256245) is 
the missing possibility to wait for "OBEX" _and_ "OBEX:IrXfer" packages. So 
please make it possible to call IrOBEX_ServerRegister() more than once on the 
same handle. Or is there another proposed solution that a single call to 
OBEX_HandleInput() could handle?

Re: openobex patches from Debian

Hi Hendrik,

> I am the current openobex maintainer for Debian and have collected some 
> patches, mainly for the apps in the package:
> 
> * docbuild.patch makes creation of the documentation possible again

was already in the CVS. However a Makefile.in should never be part of a
patch. It will be created from Makefile.am.

> * ircp.patch fixes some security related problems (although low risk, it is 
> still valid) that would overwrite files in receive mode. Instead, it adds a 
> random string to the file (using mkstemp).

I don't like using mkstemp(). Can't we simply reject it if the file
already exists?

> * obex_test.patch adds some error checking to the code and adds some missing 
> ifs for the default case

Patch has been applied to the CVS.

> * rodrigues_irobex_palm3.patch adds the possibility to specify the creation-ID 
> of the object to send

I fixed up the usage description (Using "xxxx" is not a good idea) and
you also need to include <string.h>. Look out for warnings from the
compiler.

> I also have manpages for all apps in the package. If you are interested (they 

Inclusion of .spec files

Hi!

I am interested in having .spec files in .tar.gz/bz2 packages for
openobex/obexftp/obexfs so I could build rpms for my distro with:

rpmbuild -tb *obex*tar.bz2

I slightly adjusted .spec files I found on the net:
http://2pi.waw.pl/jacek.pliszka/Linux/obex/

How can I have them or other .spec files included ?

obexftp does include one but it also includes non-typical .spec.in ...

BR,

Jacek

-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Re: Inclusion of .spec files

Hi Jacek,

> I am interested in having .spec files in .tar.gz/bz2 packages for
> openobex/obexftp/obexfs so I could build rpms for my distro with:
> 
> rpmbuild -tb *obex*tar.bz2
> 
> I slightly adjusted .spec files I found on the net:
> http://2pi.waw.pl/jacek.pliszka/Linux/obex/
> 
> How can I have them or other .spec files included ?

the *.spec files are for generating distribution specific binary
packages and I leave this to the package maintainers and thus I am not
including any *.spec files in the source packages.

Regards

Marcel

-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Re: Inclusion of .spec files

> > How can I have them or other .spec files included ?
> 
> the *.spec files are for generating distribution specific binary
> packages and I leave this to the package maintainers and thus I am not
> including any *.spec files in the source packages.

1. But I/someone could write a very generic .spec files that would
work on all distros provided user has all requirements.

2. There are .spec and .spec.in in obexftp package (moreover it is .bz2
while openobex and obexfs are .gz) so maybe we can have them in all ?

Best Regards,

Jacek

-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Re: Inclusion of .spec files

Hi Jacek,

using bzip2 for obexftp now saves a quarter of the size compared to gzip.

The .spec.in in obexftp is antique and needs a replacement. The reason 
to have Autoconf parse a spec-file is simply to avoid the duplication of 
version numbers.
If you can provide a generic rpm I'll update the obexftp one and place 
one in obexfs. OpenOBEX on the other hand is very stable and should be 
packaged by every distribution individually.

cu,
Christian

Jacek Pliszka wrote:

>1. But I/someone could write a very generic .spec files that would
>work on all distros provided user has all requirements.
>2. There are .spec and .spec.in in obexftp package (moreover it is .bz2
>while openobex and obexfs are .gz) so maybe we can have them in all ?
>  
>

-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Re: Inclusion of .spec files

Hi!

Thanks!  

I will prepare minimal .spec files for obexftp and obexfs then.

With openobex I will approach Fedora Extras.

BR,

Jacek

On Fri, 19 May 2006, Christian W. Zuckschwerdt wrote:

> Hi Jacek,
> 
> using bzip2 for obexftp now saves a quarter of the size compared to gzip.
> 
> The .spec.in in obexftp is antique and needs a replacement. The reason 
> to have Autoconf parse a spec-file is simply to avoid the duplication of 
> version numbers.
> If you can provide a generic rpm I'll update the obexftp one and place 
> one in obexfs. OpenOBEX on the other hand is very stable and should be 
> packaged by every distribution individually.
> 
> cu,
> Christian
> 
> Jacek Pliszka wrote:
> 

Re: Inclusion of .spec files

On Fri, 19 May 2006, Jacek Pliszka wrote:

>> the *.spec files are for generating distribution specific binary
>> packages and I leave this to the package maintainers and thus I am not
>> including any *.spec files in the source packages.
>
> 1. But I/someone could write a very generic .spec files that would
> work on all distros provided user has all requirements.

If your favorite package is missing from your favorite distro, you should 
persuade the vendor to include it or become a package maintainer yourself. 
Better yet, initiate/join an effort towards cross-distro repositories.

> With openobex I will approach Fedora Extras.

Openobex is already in Fedora Core and has been for a long time. Obexftp 
and obexfs aren't though, so if you would package them and integrate them 
into GNOME/KDE/other desktops' removable media infrastructure, so that the 
phone connected over USB or BT automounts just like a USB stick or a CD, 
that would be great.

Alexander

Homepage: http://www.sensi.org/~ak/

-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642