Re: outdated packages
You could also try dummy-package, or make-dummy-package, or something
like that (I've forgotten the name, and amd too lazy to go look it
up.) to create a dummy package that satisfies the dependencies that
you need. I never did get around to figuring out how to use it
though.
>>>>> "Jerry" == Jerry J Jaskierny <jaskiern@fscked.org> writes:
> thanks, i'd already thought of that. but i'd assume there has
> to be a more convenient way. debian can't possibly be built on
> just the packages and dependencies it provides.
> On 23 Mar 2000, Marshal Kar-Cheung Wong wrote:
>> Try downloading the deb source, patching the source, and then
>> using dpkg-buildpackage or dpkg --build. (Check the man
>> pages.) Make sure you get the source from the debian website
>> or with apt, if you have the deb-src lines in sources.list, as
>> it will contain debian subdirectory in the source tree, which
>> is needed by dpkg to build debs.
>>
>> Marshal
>>
>> >>>>> "Jerry" == Jerry J Jaskierny <jaskiern@fscked.org>
>> writes:
>>
>> > there are several packages included in debian archives that
>> are > outdated. instead of installing the outdated ones, in
>> some > cases are useless to me, i want to compile an updated
>> copy of > the source. i'm trying to figure out how i can
>> compile this > source, and let dpkg/dselect know that they've
>> been installed. > my first problem was alsa. i had to compile
>> and updated copy of > alsa. Esound needs to be installed with
>> support with alsa, but > dpkg doesn't know that alsa has been
>> installed, causing an > irritating chain of dependencies and
>> problems. does anyone know > how to fix this? i'm sure this
>> has been answered before, but i > couldn't find it anywhere in
>> the archives. and please reply to > this address, as i am not
>> currently subscribed to the mailing > list. thank you. jerry
>> jaskierny
>>
>>
>> > -- Unsubscribe? mail -s unsubscribe >
>> debian-user-request@lists.debian.org < /dev/null
>>
>>
Reply to: