OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Rcs (revision Control System) For Zaurus?
MB Zaurus
post Jun 16 2005, 08:08 AM
Post #1





Group: Members
Posts: 31
Joined: 16-April 05
Member No.: 6,898



Has anyone compiled RCS for the zaurus? I think it's almost indispensible for managing any system.

http://www.cs.purdue.edu/homes/trinkle/RCS/

Mark
Go to the top of the page
 
+Quote Post
MB Zaurus
post Jun 16 2005, 10:54 PM
Post #2





Group: Members
Posts: 31
Joined: 16-April 05
Member No.: 6,898



Following up on my own post:

QUOTE(MB Zaurus @ Jun 16 2005, 09:08 AM)
Has anyone compiled RCS for the zaurus? I think it's almost indispensible for managing any system.

http://www.cs.purdue.edu/homes/trinkle/RCS/

Mark
*



Thanks to the handhelds.org public development cluster (http://handhelds.org/projects/skiffcluster.html), I've built rcs, and it works fine on my SL-6000 (OE 3.5.3/Opie).

I've attached a copy of the binaries and man pagesAttached File  rcs.tar ( 570K ) Number of downloads: 52
.

Mark
Go to the top of the page
 
+Quote Post
gojira
post Aug 19 2005, 10:33 PM
Post #3





Group: Members
Posts: 124
Joined: 16-January 05
Member No.: 6,248



QUOTE(MB Zaurus @ Jun 17 2005, 05:54 PM)
I've attached a copy of the binaries and man pagesAttached File  rcs.tar ( 570K ) Number of downloads: 52
.

Mark
*


Thanks, I've been looking forward to being able to C-x v v again!

I've moved the binaries into /usr/local/bin which is where they seem to be expecting each other, and moved the man pages under /usr/local/man, and added html versions of the man pages, and packaged it up: Attached File  rcs_5.7_1_arm.ipk ( 256.71K ) Number of downloads: 36

The attachment has munged the filename. It should be rcs_5.7-1_arm.ipk.

The binaries look for diff in /usr/bin, so you'll need to add a link if yours is in /usr/local/bin. It doesn't seem to be installable onto a card. Is that because of the /usr/local paths?

This post has been edited by gojira: Aug 19 2005, 10:43 PM
Go to the top of the page
 
+Quote Post
inode0
post Aug 20 2005, 05:52 AM
Post #4





Group: Members
Posts: 97
Joined: 15-December 04
Member No.: 5,933



QUOTE(gojira @ Aug 20 2005, 06:33 AM)
The binaries look for diff in /usr/bin, so you'll need to add a link if yours is in /usr/local/bin.  It doesn't seem to be installable onto a card.  Is that because of the /usr/local paths?

You might take a look at the package in this feed which should work fine mounted on a card. It depends on diffutils which is in the same feed but as long as you have diff in your path it should be ok I think.

John
Go to the top of the page
 
+Quote Post
gojira
post Aug 21 2005, 04:45 PM
Post #5





Group: Members
Posts: 124
Joined: 16-January 05
Member No.: 6,248



QUOTE(inode0 @ Aug 21 2005, 12:52 AM)
]You might take a look at the package in this feed which should work fine mounted on a card. It depends on diffutils which is in the same feed but as long as you have diff in your path it should be ok I think.
John
*


The package I built will install onto a card too if you use ipkg -d and change your path, but not if you use qinstall, which seems to first install into the builtin flash, then move it to a card and add symlinks, but I think it only does that for stuff under /home/QtPalmtop...

The build of rcs I used had the full path set for diff, so unless you built it differently it probably won't look it up in the path.

Thanks for pointing out your feed -- I hadn't come across it before.
Go to the top of the page
 
+Quote Post
inode0
post Aug 21 2005, 06:05 PM
Post #6





Group: Members
Posts: 97
Joined: 15-December 04
Member No.: 5,933



QUOTE(gojira @ Aug 22 2005, 12:45 AM)
The build of rcs I used had the full path set for diff, so unless you built it differently it probably won't look it up in the path.

Oops ... goes back to fix this broken package.

Thanks
John
Go to the top of the page
 
+Quote Post
inode0
post Aug 21 2005, 07:00 PM
Post #7





Group: Members
Posts: 97
Joined: 15-December 04
Member No.: 5,933



QUOTE(inode0 @ Aug 22 2005, 02:05 AM)
QUOTE(gojira @ Aug 22 2005, 12:45 AM)
The build of rcs I used had the full path set for diff, so unless you built it differently it probably won't look it up in the path.

Oops ... goes back to fix this broken package.

Let me ask if this seems a reasonable solution?

In diffutils' postinst make links from /usr/bin/diff and /usr/bin/diff3 to wherever they are really installed and in rcs' postinst do likewise for co and merge. Have all hardcoded paths in the rcs package point to /usr/bin and clean up the links in the postrm for each package.

John
Go to the top of the page
 
+Quote Post
gojira
post Aug 25 2005, 12:10 AM
Post #8





Group: Members
Posts: 124
Joined: 16-January 05
Member No.: 6,248



QUOTE(inode0 @ Aug 22 2005, 02:00 PM)
Let me ask if this seems a reasonable solution?

In diffutils' postinst make links from /usr/bin/diff and /usr/bin/diff3 to wherever they are really installed and in rcs' postinst do likewise for co and merge. Have all hardcoded paths in the rcs package point to /usr/bin and clean up the links in the postrm for each package.

John
*


I guess there's three more or less reasonable options:

a) package with postinst and postrm symlink management between expected location and location on card for compiled in paths, ipkg -d, add location on card to path

b) modify code to use execlp or execvp, ipkg -d, add location on card to path

c) set autoconf --prefix (for compiled in paths) to, and package under, /home/QtPalmtop (or whatever is the correct path for packages ending up there), qinstall

I don't think any of them really win, so you might as well go with your option a). I've been considering something involving stow with no need to work out which links are needed or to add to the path, but I've only got half-baked ideas so far...
Go to the top of the page
 
+Quote Post
inode0
post Aug 30 2005, 11:53 AM
Post #9





Group: Members
Posts: 97
Joined: 15-December 04
Member No.: 5,933



QUOTE(gojira @ Aug 25 2005, 08:10 AM)
I guess there's three more or less reasonable options:

a) package with postinst and postrm symlink management between expected location and location on card for compiled in paths, ipkg -d, add location on card to path

I don't think any of them really win, so you might as well go with your option a).

Ok, thanks for the feedback. I have reworked the necessary packages now and am in the process of repackaging everything in the feed into what I believe is a much better organization for most people.

Basically the new organization will be to split packages into foo_X.Y-Z_arm.ipk, foo-doc_X.Y-Z_arm.ipk, and foo-dev_X.Y-Z_arm.ipk where you basically get binaries in foo, info/man/docs in foo-doc, and development files in foo-dev. All packages house required license related files in the CONTROL tarball.

rcs_5.7-1.arm.ipk now manages links for co and merge and depends on diffutils, which in turn manages links for diff and diff3 and depends on coreutils and librt, and coreutils manages a link for pr required by diff. Yuck! I'm not very happy with needing coreutils to use rcs, but there is a chain of dependencies ...

John
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 20th August 2014 - 06:23 PM