How do I get apt to know about self-compiled software
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How do I get apt to know about self-compiled software
If I have downloaded source and compiled it myself, how do those packages in the database that apt uses.
apt-get update only checks for new lists on the sites specified on sources.list right?
thanks zuralin but now I've run into another problem with equivs. Having done a "equivs-control filename" and changing the package accordingly I try to do a "equivs-build filename" and get the following error message:
Possible precedence problem on bitwise & operator at /usr/bin/equivs-build line 71.
Possible precedence problem on bitwise & operator at /usr/bin/equivs-build line 179.
Error on copying <additionalfilesforthedocdirectory to /home/user/test/equivs/docs/<additionalfilesforthedocdirectory : No such file or directory at /usr/bin/equivs-build line 98, <IN> line 43.
I got past that problem but still the equiv wont build right. Here's the ouput when trying to build it:
Possible precedence problem on bitwise & operator at /usr/bin/equivs-build line 71.
Possible precedence problem on bitwise & operator at /usr/bin/equivs-build line 179.
dh_testdir
touch build-stamp
dh_testdir
dh_testroot
dh_clean -k
# Add here commands to install the package into debian/tmp.
touch install-stamp
dh_testdir
dh_testroot
dh_installdocs
dh_installchangelogs
parsechangelog/debian: error: badly formatted heading line, at changelog line 1
dh_installchangelogs: changelog parse failure
make: *** [binary-arch] Error 1
Error during the build process: Inappropriate ioctl for device at /usr/bin/equivs-build line 180, <IN> line 31.
Haven't checked here for a while and had almost given up on this thread...
I'm trying to build an equiv (or whatever they are called in singularis) for mplayer and the control file looks like this:
get rid of the <> around your package and provides fields.
I suspect (by observing the changelogs of actual debian packages) that the <> around the version field should be removed as well but it builded for me with the <> around version.
After the changes, your control file should look like this:
That acctually worked. Thought I had tried something like that on the way but I guess I just took for granted it would ignore the <>
Anyway, thanks for helping!
Just found something that might help you in the future with equivs.
the man page for deb-control has a description of the format for control files and an example.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.