Re: Exciting Pilot/Debian news
Behan Webster <[EMAIL PROTECTED]> writes: > John Goerzen wrote: > > > > pilot-manager -- Perl/TK hotsync tool (waiting for me to download and > > try it out) > > pilot-manager is already packaged. In fact I've been using it for weeks > already. I went back and ran a find in the main FTP area on master and in Incoming and found no pilot-manager package. Where is this? -- John Goerzen Linux, Unix consulting & programming [EMAIL PROTECTED] | Developer, Debian GNU/Linux (Free powerful OS upgrade) www.debian.org | + Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
It's probably going to stay like that until the upstream kpilot maintainer fixes the build process, which is a mess at this point. I spent a couple hours trying to fix it but got nowhere so I will just leave it as-is at the moment :-) John Ben Gertzfield <[EMAIL PROTECTED]> writes: > > "John" == John Goerzen <[EMAIL PROTECTED]> writes: > > John> kpilot -- KDE hotsync tool > > Hm.. kpilot seems to have been statically linked with libpisock. > > [EMAIL PROTECTED]:~]% dpkg -l 'libpi*' > 1:38PM > Desired=Unknown/Install/Remove/Purge > | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > uppercase=bad) > ||/ NameVersionDescription > +++-===-==- > ii libpisock-dev 0.8.11-1 static libraries for communicating with a > Pi > ii libpisock3 0.8.11-1 Libraries for communicating with a Pilot > PDA > > but kpilot doesn't depend on libpisock3 -- perhaps it's not dynamically > linked? It should be, though. > > [EMAIL PROTECTED]:~]% dpkg --status kpilot > 1:38PM > Package: kpilot > Status: install ok installed > Installed-Size: 1207 > Maintainer: John Goerzen <[EMAIL PROTECTED]> > Version: 3.0.2-1 > Depends: kdelibs0g (>= 2:980312), libc6, libstdc++2.8 (>= 2.90.26-1), qt1g > (>= 1.33-5), xlib6g (>= 3.3-5) > Description: PalmPilot/III hotsync package > Kpilot provides file transfer and sync capabilities for owners of > the 3COM PalmPilot or Palm III PDAs. It currently includes conduits > for mail, datebook, and memo pad. > > Also, kpilot for some reason includes a lot of extra files, like: > > /usr/X11R6/lib/libpisock.a > /usr/X11R6/lib/libpisock.la > > Yuck! Those shouldn't be in there. > > Good luck. > > -- > Brought to you by the letters P and V and the number 19. > "I'm with insurance." -- 12 Monkeys > Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ > I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. > -- John Goerzen Linux, Unix consulting & programming [EMAIL PROTECTED] | Developer, Debian GNU/Linux (Free powerful OS upgrade) www.debian.org | + Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
John Goerzen <[EMAIL PROTECTED]> writes: > I am wondering if it might be a good idea to make a pilot, pda, palm, > portable, or something category in the FTP site so these things can > get out of otherosfs, which doesn't really apply very well. Personally, I think it isn't too bad a fit, but there does seem to be a small bit of inconsistency on where stuff like this should go: - casio (a sync utility for casio organizers) is in comm - p3nfs (mounts Psion palmtop as a file system) is in admin - libpisock3 is in libs - pilot-link-{dev,perl,tcl} are in devel - pilot-link is in otherosfs Now, add to this kpilot, pilot-manager, prc-tools, palmpython(*), xmldoc(*), and whatever other PDA-related tools are yet to be Debianized (I know there is Unix stuff for the Newton, probably more than p3nfs for the Psion, etc.) and there might be the potential for even more confusion if everything isn't in more or less the same place. I don't think making a new section for PDA-related stuff would be a bad idea, but otherosfs is still small enough that it might be more trouble to create a new section than it is worth. (I have no idea how easy or tough it is to do so; it seems like it might be non-trivial.) (*) palmpython and xmldoc are my own applications, which ought to be Debianized very soon, as soon as I iron out some kinks in the build process. --Rob -- Rob Tillotson N9MTBInternet: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
Hmmm, perhaps it's still in incoming, since it is not listed at all in my /var/lib/dpkg/available file... weird But in any case, I won't bother with it then :-) I am wondering if it might be a good idea to make a pilot, pda, palm, portable, or something category in the FTP site so these things can get out of otherosfs, which doesn't really apply very well. John Behan Webster <[EMAIL PROTECTED]> writes: > John Goerzen wrote: > > > > pilot-manager -- Perl/TK hotsync tool (waiting for me to download and > > try it out) > > pilot-manager is already packaged. In fact I've been using it for weeks > already. > > > griffon:~> dpkg --status pilot-manager > Package: pilot-manager > Status: install ok installed > Installed-Size: 323 > Maintainer: Darren Stalder <[EMAIL PROTECTED]> > Version: 1.106-0.1 > Depends: perl, pilot-link-perl, perl-tk, data-dumper > Recommends: pilot-link > Suggests: plan > Description: PalmPilot PIM, UI, and Conduit Manager > PilotManager is a tool that allows you to synchronize databases on your > 3Com PalmPilot with applications on your Unix platform. It is a full > Hotsync daemon that is user extensible. Developers can write their own > conduits to synchronize Pilot databases with the desktop application of > their choice. > > griffon:~> > > Behan > > -- > Behan Webster mailto:[EMAIL PROTECTED] > +1-613-224-7547 http://www.verisim.com/ > -- John Goerzen Linux, Unix consulting & programming [EMAIL PROTECTED] | Developer, Debian GNU/Linux (Free powerful OS upgrade) www.debian.org | + Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
Hamish Moffatt <[EMAIL PROTECTED]> writes: > On Wed, Jun 17, 1998 at 03:13:27PM -0500, John Goerzen wrote: > > Therefore, I believe that I will just dump the tar.gz's of binutils, > > gcc, and gdb into the toplevel of the package's tar file (or maybe the > > debian/ directory, I dunno), and then all I have to do is change the > > path that it looks for them from .. to . > > Won't this give a humongous source tree? Well yes, this is why I didn't include them before. But it's better than including all of the file uncompressed. > I'm wondering what the best way to make cross-compilers available is. > Sometimes the upstream source might be just the gcc source. Perhaps, > when/if we get real source packages, we can have diff.gz/dsc files > for .orig.tar.gz files of different names, so that I could build > a diff.gz/dsc file to build a .deb file, but use the gcc.orig.tar.gz > source. In this case, it won't work since prc-tools patches the upstream, and then I patch the patch :-) Also, prc-tools contains some binary files, and our diff mechanism currently cannot handle that. -- John Goerzen Linux, Unix consulting & programming [EMAIL PROTECTED] | Developer, Debian GNU/Linux (Free powerful OS upgrade) www.debian.org | + Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
On Wed, Jun 17, 1998 at 03:13:27PM -0500, John Goerzen wrote: > Therefore, I believe that I will just dump the tar.gz's of binutils, > gcc, and gdb into the toplevel of the package's tar file (or maybe the > debian/ directory, I dunno), and then all I have to do is change the > path that it looks for them from .. to . Won't this give a humongous source tree? I'm wondering what the best way to make cross-compilers available is. Sometimes the upstream source might be just the gcc source. Perhaps, when/if we get real source packages, we can have diff.gz/dsc files for .orig.tar.gz files of different names, so that I could build a diff.gz/dsc file to build a .deb file, but use the gcc.orig.tar.gz source. Hamish -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
> "Rob" == Rob Tillotson <[EMAIL PROTECTED]> writes: Rob> Kpilot comes with its own version of libpisock, which is Rob> built and statically linked independent of whether you have Rob> another one already on the system. I haven't looked deeply Rob> at the code, but I would assume that the kpilot author has Rob> made some changes to the library which justify this. Well, in any case, it shouldn't include the .a and .la files, as they're linked in. -- Brought to you by the letters S and C and the number 2. "You should be glad you don't have diaper rash. Mah Jongg." -- The Critic Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
Ben Gertzfield <[EMAIL PROTECTED]> writes: > but kpilot doesn't depend on libpisock3 -- perhaps it's not dynamically > linked? It should be, though. Kpilot comes with its own version of libpisock, which is built and statically linked independent of whether you have another one already on the system. I haven't looked deeply at the code, but I would assume that the kpilot author has made some changes to the library which justify this. --Rob -- Rob Tillotson N9MTBInternet: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
John Goerzen wrote: > > pilot-manager -- Perl/TK hotsync tool (waiting for me to download and > try it out) pilot-manager is already packaged. In fact I've been using it for weeks already. griffon:~> dpkg --status pilot-manager Package: pilot-manager Status: install ok installed Installed-Size: 323 Maintainer: Darren Stalder <[EMAIL PROTECTED]> Version: 1.106-0.1 Depends: perl, pilot-link-perl, perl-tk, data-dumper Recommends: pilot-link Suggests: plan Description: PalmPilot PIM, UI, and Conduit Manager PilotManager is a tool that allows you to synchronize databases on your 3Com PalmPilot with applications on your Unix platform. It is a full Hotsync daemon that is user extensible. Developers can write their own conduits to synchronize Pilot databases with the desktop application of their choice. griffon:~> Behan -- Behan Webster mailto:[EMAIL PROTECTED] +1-613-224-7547 http://www.verisim.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
> "John" == John Goerzen <[EMAIL PROTECTED]> writes: John> Therefore, I believe that I will just dump the tar.gz's of John> binutils, gcc, and gdb into the toplevel of the package's John> tar file (or maybe the debian/ directory, I dunno), and then John> all I have to do is change the path that it looks for them John> from .. to . This seems to be a good solution. Good luck. :) -- Brought to you by the letters C and I and the number 17. "Wakarimasu ka?" "Ee!" "Wakarimasen ka." "Ee." -- Tenchi Muyo-! Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
> "John" == John Goerzen <[EMAIL PROTECTED]> writes: John> kpilot -- KDE hotsync tool Hm.. kpilot seems to have been statically linked with libpisock. [EMAIL PROTECTED]:~]% dpkg -l 'libpi*' 1:38PM Desired=Unknown/Install/Remove/Purge | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ NameVersionDescription +++-===-==- ii libpisock-dev 0.8.11-1 static libraries for communicating with a Pi ii libpisock3 0.8.11-1 Libraries for communicating with a Pilot PDA but kpilot doesn't depend on libpisock3 -- perhaps it's not dynamically linked? It should be, though. [EMAIL PROTECTED]:~]% dpkg --status kpilot 1:38PM Package: kpilot Status: install ok installed Installed-Size: 1207 Maintainer: John Goerzen <[EMAIL PROTECTED]> Version: 3.0.2-1 Depends: kdelibs0g (>= 2:980312), libc6, libstdc++2.8 (>= 2.90.26-1), qt1g (>= 1.33-5), xlib6g (>= 3.3-5) Description: PalmPilot/III hotsync package Kpilot provides file transfer and sync capabilities for owners of the 3COM PalmPilot or Palm III PDAs. It currently includes conduits for mail, datebook, and memo pad. Also, kpilot for some reason includes a lot of extra files, like: /usr/X11R6/lib/libpisock.a /usr/X11R6/lib/libpisock.la Yuck! Those shouldn't be in there. Good luck. -- Brought to you by the letters P and V and the number 19. "I'm with insurance." -- 12 Monkeys Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
Ben Gertzfield <[EMAIL PROTECTED]> writes: > John> I'd like feedback on it. I have opted to package it as it > John> is done upstream; that is, all the programs in one thing. > > Okay, here's a bit of feedback. :) > > prc-tools includes almost all of its files in /usr/m68k-palmos-coff/, > except two: > > gilgamesh:/home/che# dpkg --contents prc-tools_0.5.0-2_i386.deb > > *snip* > > -rw-r--r-- root/root142336 1998-06-16 13:54 usr/lib/libreadline.a > -rw-r--r-- root/root 20270 1998-06-16 13:54 usr/lib/libmmalloc.a This I've already fixed. There is now an -2 or -3 or so release of prc-tools in Incoming. These are not actually for the Pilot; these were built by gdb for i386, I believe, and AFAIK they are not necessary for anything except building gdb. My debian/rules has to delete a lot of stuff like that from the stuff to be installed and I happened to miss those two. > This makes it impossible to install prc-tools if you have > libreadlineg2-dev or any other package that has libmmalloc.a included > (not sure what this is offhand). Yeah. I went through about 5 compiles of -1 before I thought I had it cleared up. And I still missed those two :-) (At 30-40 mins per compile [100+ meg source tree], that took awhile) > These two should be moved into /usr/m68k-palmos-coff/. Actually, they're deleted :-) > This is a hard one; I think the point of a source package is to > have *everything* you need to build the target. If you have to > download other things, it becomes difficult quickly. This is a good point. Also I don't want 100+ meg of files cluttering up my cvs tree. > I'm not sure what the right solution is. I think I know what it is now. I want to make as few modifications as possible to the upstream. What it likes to do is untar binutils, gcc, and gdb; modify them; compile them; and then install them. If I were to include the modified gcc and gdb stuff (so that building the package only requires compiling and installing), upgrades would be a pain, and I worry about the ethics of including modified sources in the orig. Therefore, I believe that I will just dump the tar.gz's of binutils, gcc, and gdb into the toplevel of the package's tar file (or maybe the debian/ directory, I dunno), and then all I have to do is change the path that it looks for them from .. to . I have to use the very specific version that the prc-tools is contains patches for; others won't work. So there isn't really any good way to share code with the native gcc packages -- the native ones usually stay a few versions ahead. John -- John Goerzen Linux, Unix consulting & programming [EMAIL PROTECTED] | Developer, Debian GNU/Linux (Free powerful OS upgrade) www.debian.org | + Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
Ben Gertzfield <[EMAIL PROTECTED]> writes: > John> etc. packages for Debian. The package name is prc-tools and > John> should be in Incoming by the time you read this. It was > John> quite a chore to package but it is quite exciting what can > John> be done with it! > > Wonderful news, John! Congratulations. > > I'll try out these packages later today. This is pretty exciting; > I've been waiting for pilot development tools for quite a while. :) Hehe :-) So far, I've built: kpilot-- KDE hotsync tool pilrc -- Pilot resource compiler plus GUI prc-tools -- cross-compilation environment imgvtopgm -- Converter to make graphics suitable for ImageViewer or Spec (freeware clone). Nice to viewing maps on the Pilot; four shades of gray. I hope to have the following in a few days: makedoc7 -- Converts text files to PRC DOC format for viewing on the Pilot (on hold waiting for reply from author on license) pilot-manager -- Perl/TK hotsync tool (waiting for me to download and try it out) Others have already packaged pilot-link and pui, so we will shortly have a full suite of Pilot tools available. > I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. Ahh cool, I'm CosmicRay on LinPeople. -- John Goerzen Linux, Unix consulting & programming [EMAIL PROTECTED] | Developer, Debian GNU/Linux (Free powerful OS upgrade) www.debian.org | + Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
> "John" == John Goerzen <[EMAIL PROTECTED]> writes: John> Hi, I have now successfully built the GCC, gdb, binutils, John> etc. packages for Debian. The package name is prc-tools and John> should be in Incoming by the time you read this. It was John> quite a chore to package but it is quite exciting what can John> be done with it! John> I'd like feedback on it. I have opted to package it as it John> is done upstream; that is, all the programs in one thing. Okay, here's a bit of feedback. :) prc-tools includes almost all of its files in /usr/m68k-palmos-coff/, except two: gilgamesh:/home/che# dpkg --contents prc-tools_0.5.0-2_i386.deb *snip* -rw-r--r-- root/root142336 1998-06-16 13:54 usr/lib/libreadline.a -rw-r--r-- root/root 20270 1998-06-16 13:54 usr/lib/libmmalloc.a *snip* This makes it impossible to install prc-tools if you have libreadlineg2-dev or any other package that has libmmalloc.a included (not sure what this is offhand). These two should be moved into /usr/m68k-palmos-coff/. John> The upstream prc-tools consists of patches against gcc, John> binutils, and gdb plus its own software. The prc-tools John> source package does not include the gcc, binutils, and gdb John> source itself. Is this correct? This is a hard one; I think the point of a source package is to have *everything* you need to build the target. If you have to download other things, it becomes difficult quickly. I'm not sure what the right solution is. -- Brought to you by the letters C and M and the number 2. "It is sad. *Campers* cannot *dance*. Not even a *party*." -- Orz, SCII Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Exciting Pilot/Debian news
> "John" == John Goerzen <[EMAIL PROTECTED]> writes: John> Hi, I have now successfully built the GCC, gdb, binutils, John> etc. packages for Debian. The package name is prc-tools and John> should be in Incoming by the time you read this. It was John> quite a chore to package but it is quite exciting what can John> be done with it! Wonderful news, John! Congratulations. I'll try out these packages later today. This is pretty exciting; I've been waiting for pilot development tools for quite a while. :) -- Brought to you by the letters O and S and the number 2. "O, Mentos Boy!" -- Guppy Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Exciting Pilot/Debian news
Hi, I have now successfully built the GCC, gdb, binutils, etc. packages for Debian. The package name is prc-tools and should be in Incoming by the time you read this. It was quite a chore to package but it is quite exciting what can be done with it! I'd like feedback on it. I have opted to package it as it is done upstream; that is, all the programs in one thing. The upstream prc-tools consists of patches against gcc, binutils, and gdb plus its own software. The prc-tools source package does not include the gcc, binutils, and gdb source itself. Is this correct? Also, it replaces, provides, and conflicts the previous gcc-m68k-palmos-coff and current binutils-m68k-palmos-coff packages. Again, is this correct? Thanks, John -- John Goerzen Linux, Unix consulting & programming [EMAIL PROTECTED] | Developer, Debian GNU/Linux (Free powerful OS upgrade) www.debian.org | + Visit the Air Capitol Linux Users Group on the web at http://www.aclug.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]