cbagger01

Group: Members
Posts: 4264
Joined: Oct. 2003 |
 |
Posted: Sep. 20 2004,16:26 |
 |
The main reason why you should always run the deb2dsl script from a fresh livecd/frugal/poorman's boot is because the script will grab all existing *.deb files in the apt archives and build them into a *.dsl file.
This will get all of the required dependencies for your new application.
If you do this from a hd-install or even a livecd install after you have installed/removed stuff using apt-get or Synaptic, the archives directory will no longer contain an accurate list of the packages that are needed to install your application into a base install of the DSL distro.
So to make a short answer long:
You can do it from an hd-install but ONLY if the install is fresh and you have not added or removed anything via apt-get/dpkg/Synaptic.
And of course this is a one-shot deal because after you have used deb2dsl and apt-get once to build a package, you no longer have a fresh install anymore so you cannot build a second *.dsl file for a different program without accidentally including the stuff from your first program.
|