ipkg-link doesn't obey /etc/ipkg.conf dest entries

[lardman]

ipkg-link is a script and it's hard-coded with the 'dest' locations.

If I decided to create a new installation point (by adding the dest ... line to /etc/ipkg.conf) this is not picked up by ipkg-link.

This is not a major issue unless you have a C machine and want to use your /home directory to install stuff too.

Has this been fixed in a later version or shall I set to work updating it?

Cheers,


Si

[zenyatta]

Hmmm... suddenly a couple of things fall into place... Thanks for the footwork so far.

z.

[jesizmi]

could this be the reason that all my attempts failed, to make my 2nd partition of my SD the target for installation on SD?
I added the dest line to ipkg.conf but still every installation was placed in card (mmcda1)

Tx for reply

j.

[lardman]

Depends what you mean by fail; the files should have been installed correctly, but they just wouldn't have been linked (and so wouldn't have worked).

This isn't what your problem sounds like (everything was placed in /dev/mmcda1). Where was your mount point (was it mounted correctly, etc.)? What command line options did you use?


Si

[jesizmi]

No command line options as far as i'm aware of, since i use the graphical ipkg  installer. When asked where to install, i chose SD from the popup.

But i improved the situation by tweaking sdcontrol and fstab, so that now mmcda1 is mounted to /mnt/card2 and mmcda2 to /mnt/card. Now I'm able to install to the ext2-partition. The draw back is, that PC-Link in storage mode as well tries to get on mmcda2, witch with windows does no good.
But i can live with that. I just thought it would be nice to have things properly arranged and everything in the right place.

[Bundabrg]

For testing, I've modified ipkg-link. It now parses /etc/ipkg.conf. It (should) remain parameter compatible with programs that use existing ipkg-link.

IPKG Update

 - Bundabrg

[lardman]

Does this still hold true with OZ3.5.1?

If so, Bundabrg, you should submit a patch to the current ipkg-link (though I've no idea where it lies).

If someone can confirm that the standard ipkg-link still doesn't use /etc/ipkg.conf then I'll do some digging and work how ipkg-link is created by OE.


Si

[Bundabrg]

I'm running 3.5.1, and yes it has the stuff hard coded in.

My file above is for 3.5.1 though I suspect it will work for all versions that use ipkg-link since its really just a simple shell script.

I have no idea where to submit the file, but I was hoping to have it tested a bit whilst I figure that one out ;-)

 - Bundabrg

[ironstorm]

That's funny...  

I just had the same thought myself and rewrote ipkg-link the other night to do the same thing...

http://stacktrace.org/index_html/ipkg-link2

oh well...   one thing I added was check to make sure that the mount points are all valid...  

Cheers

-G

[Bundabrg]

Ahh but can it wash the dishes as well ;-)

 - Bundabrg

[awaldram]

I think your getting confused

thated be ipkg-sink not ipkg-link

[Bundabrg]

Whoops, my mistake.

 - Bundabrg

[_Psycho]

Thanks for the fix, worked great

[donotresus]

I think my problem falls under here.

I am trying to install my programs to the CF card I have, I followed the instructions on the thread titled Steps to a Package Manager under 3.5.1

However, the linking always fails. I always get an Operation Not Permitted error anytime ipkg-link or ln is called on the cf card. I have updated my ipkg-link script to the first one posted here.

This is meaning I can't install any software

Can anyone help?

Dave

[dansawyer]

Maybe,

How is the CF card formatted? It is probably formated as DOS or VFAT. In order for 'links' to work the destination must be formatted as ext2. This is a common problem with installing packages to sd cards. I assume it is the same for CF.

I have never formatted a CF to ext2 it. I suspect it should work.

Dan