Apt-get :: problems saving Debian packages between sessions



You could install one debian package and then run deb2dsl, although I'm only guessing...I've never done much with debian packages, and nothing with apt-get.

Another option is to extract the deb file you want and manually build a dsl or unc file from that.
Quote (mikshaw @ May 25 2007,17:10)
Another option is to extract the deb file you want and manually build a dsl or unc file from that.

Actually, this is what I did.  I hacked deb2dsl so it creates a separate .dsl for each .deb .  And it works great.  (I finally figured out that those .dsl files are just .tgz (or .tar.gz as is your preference).)

OK, one problem down, many, many more to go...
Quote (robertakit @ May 25 2007,18:20)
(I finally figured out that those .dsl files are just .tgz (or .tar.gz as is your preference).)

Yes, in fact you can rename it, and it loads either way.  Maybe someone can say if there are any differences?  The only thing I can think of, is that help files, etc., should be stripped out to be true dsl apps.
The filenames *.dsl and *.tar.gz work with mydsl-load, but I don't believe *.tgz is recognized by the script. I see it in the auto-load part of /etc/init.d/dsl-config, but it seems to be handled the same as a *.dsl.

There are differences in how they are loaded depending on the filename, regardless of the fact that the files themselves are identical.

First, *.dsl files cause the mkwritable script to run, but *.tar.gz files do not. This script opens up more of the system for writing, and increases memory and inode usage.

Second, *.tar.gz extensions do not write to the parts of the system that are intially read-only in DSL. If you were to rename all of your *.dsl files to *.tar.gz they will usually fail to load during boot.

Third, just to emphasis an important aspect of building extensions, the *.dsl and *.tar.gz packages are _not_ simply gzipped tarballs. They must not contain directories that already exist in DSL unless those directories have the same ownership and permissions of the originals. This may break your system, including possible security meltdown, broken applications, or complete system failure.
Quote (mikshaw @ May 30 2007,23:47)
First, *.dsl files cause the mkwritable script to run, but *.tar.gz files do not. This script opens up more of the system for writing, and increases memory and inode usage.

Second, *.tar.gz extensions do not write to the parts of the system that are intially read-only in DSL.

So as a rule it would be a good idea to change the extension on a compiled .tar.gz app? BTW, thanks for this info.  I was never very clear on the purpose of "inodes"  other than to create problems.
Next Page...
original here.