forums.xandros.com

jimallyn

Since there are a number of us making DEB packages now, and there are 4 different versions of Xandros out there now, it occurs to me that we should put the Xandros version the DEB was compiled for in the package name. This came to mind the other day when it was (accidentally) suggested that someone install a package I compiled for X4 on X3. So, perhaps we should include Xandros version in the package name so it's visible at a glance, like so:

someapp-1.2.5_X4_i386.deb

someapp-1.2.5_X3_i386.deb

someapp-1.2.5_X2_i386.deb

This would make it clear which version of Xandros the package is intended for.

It would be good if we all did this the same way. Comments or suggestions?

Jim
_________________
I refuse to live in a country like this - and I'm not leaving. - Michael Moore

papabearak · Posted: Tue Mar 27, 2007 4:24 pm Post subject:

I agree, Jim. Although I personally am in no imminent danger of creating any debs myself, I hope those who do so will adopt the convention you outlined. It could prevent a few fatal errors, always a good thing in my book. Ben Smile

_________________

Using Klikit-Linux ver. 0.1-8, all day, every day.
Check out Xandros Wiki - Lots of good stuff
http://geekconnection.pbwiki.com/Xandros%20Wiki%20Resource%20Page

Arne Anka

jimallyn

geekydude · Posted: Tue Mar 27, 2007 5:45 pm Post subject:

Good advice to us deb building noobs! Razz

_________________
geekydude
registered Linux user number 410045.

The source will be with you...always....

redrum · Posted: Tue Mar 27, 2007 6:16 pm Post subject:

The most important part of building packages is trying to keep the wrong users from installing the packages in the first place.. Dependencies really help in that regard, because if the system doesn't have the necessary dependencies, the package simply won't install...

On packages using checkinstall, the best thing is to declare the target audience.. If someone installs the package after being told it won't work on their version of Xandros, well-- its kind of their own fault.. If it wasn't declared, that's the author's fault.. Please edit any posts with packages built using checkinstall and include the target audience..

My personal routine involves a few steps before releasing a package... Sometimes I bend 'em a bit, but for the most part I follow this protocol.

1. Build the package with what dependencies you know the user will need (mmmm, yeah, kinda have to have the package Smile

) .
2. Fire up vmware, and install the package on the most stripped down version of Xandros that is allowed by the installer. (For the image, you will want to make a snapshot of the install after rebooting the OS twice inside vmware). If it bombs, click the 'revert to snapshot' option in VMWare to restore your 'minimal Xandros install' image and go to step 1. If it installs OK and doesn't unintentionally break anything, in the process, go to step 3.
3. Run the program and see if any libraries are needed. If it runs well, click the 'revert to snapshot' option in VMWare to restore your 'minimal Xandros install' image and go to step 8. If it does not, go to step 4.
4. Install the necessary packages to satisfy all of the program's functions.
5. Make a list of those libraries and the packages they come from. Also click the 'revert to snapshot' option in VMWare to restore your 'minimal Xandros install' image.
6. Rebuild the package.
7. Go to 2.
8. Upload your file (yay!)
9. Carefully prepare your post, including the target audience for the package, any known issues, and how to undo the changes caused by the package (if applicable).
10. Make available time for first installers to comment on the file.. If there are issues, fix them asap. For those with busy work days, choose off days to release your packages.
_________________

Beware of the man who would deny you access to information,
for in his heart he dreams himself your master.

geekydude · Posted: Tue Mar 27, 2007 6:48 pm Post subject:

Thanks for the handy step by step process! Very Happy

_________________
geekydude
registered Linux user number 410045.

The source will be with you...always....

scott · Posted: Tue Apr 10, 2007 5:17 pm Post subject:

redrum: This is a little off topic for this thread. Were you able to get VMware tools to install though XN? I just installed 4.0+SP1. I'm showing VMware tools installed in expert alien but VMware tells me it's not installed. To I need to do this using the tar option? This sounds like a very good way to try out new things and such.
Thanks Scott
_________________
[img]http://img406.imag
eshack.us/img406/1995/tuxclockdp6.jpg[/img]
Dual booting Xandros 4.1 and Klikit 1.5a
http://www.scrollsawart.com

redrum · Posted: Wed Apr 11, 2007 3:31 am Post subject:

You have to run vmware-config.pl as root to get vmware to work after installing the rpm... Go with the default options (hit enter like a chicken pecks the ground and it should give you a workable install...) Kernel-headers and c++ development tools must be installed as well..

If you have gotten it to work but you just want to add the vmware-tools package, to be honest I have no idea as it seems unnecessary to do the task at hand. In other words, I don't use them, and have found no use for them...

Hope this helps.
_________________

Beware of the man who would deny you access to information,
for in his heart he dreams himself your master.

scott · Posted: Wed Apr 11, 2007 7:05 am Post subject:

Thanks redrum the light bulb finally went on in this old head off mine, installed the headers and c++ then installed from the console su. I guess you are right about not needing it for just test and building things. I'm on a laptop so thought it would be nice to have a full screen at 1280X800, for some reason it didn't work to get this resolution. It worked with XP in VM.
I'm sure glad I read your post, there is somethings I want to try but was afraid to, now I don't care if I hose this VM, do have a snapshot of the setup.
_________________
[img]http://img406.imag
eshack.us/img406/1995/tuxclockdp6.jpg[/img]
Dual booting Xandros 4.1 and Klikit 1.5a
http://www.scrollsawart.com