On 2003-11-11 06:55:36 +0800, csj wrote:
> You might try creating your own apt archive. An apt archive is just a
> directory (or subdirectories) full of debs. To make them visible
> to apt you create an index file called Packages (or gzipped to
> Packages.gz) using a command like "dpkg-scanpackag
On Mon, 10 Nov 2003 12:42:02 +0100,
Vincent Lefevre wrote:
>
> What is the best way to compile and install packages from source with
> apt?
>
> I don't want to use "dpkg -i" once the packages are built (as suggested
> in the how-to) since dpkg doesn't check dependencies and may break the
> system
On 2003-11-10 11:15:26 -0500, David Z Maze wrote:
> dpkg does *check* dependencies, it just doesn't go out of its way to
> *correct* them. That is, dpkg shouldn't let you install a package if
> its dependencies aren't already installed. If you never use a --force
> option and your packages work,
Vincent Lefevre <[EMAIL PROTECTED]> writes:
> What is the best way to compile and install packages from source with
> apt?
>
> I don't want to use "dpkg -i" once the packages are built (as suggested
> in the how-to) since dpkg doesn't check dependencies and may break the
> system (it did in the pa
What is the best way to compile and install packages from source with
apt?
I don't want to use "dpkg -i" once the packages are built (as suggested
in the how-to) since dpkg doesn't check dependencies and may break the
system (it did in the past...).
--
Vincent Lefèvre <[EMAIL PROTECTED]> - Web:
5 matches
Mail list logo
