Re: [auto-apt and build-dep] (was: MacBook Air, Catalina: after fink installation sudo apt-get update fails)
Alexander Hansen <[email protected]>
| Newsgroups | gmane.os.apple.fink.beginners |
|---|---|
| Message-ID | <[email protected]> |
On 2/19/2021 1:50 PM, Uwe Brauer wrote: >> On 2/19/2021 1:07 PM, Uwe Brauer wrote: >> Honestly, I wish we had forked dpkg and apt back in the beginning of >> Fink and used different names for the executables. This would help us >> manage the expectations of people coming over from Debian-like Linux >> distros. > > Hm, indeed. > > >> As was mentioned before, there's no binary distribution for 10.15, so >> apt-get isn't going to help you install packages. Try "fink install >> git" instead. > Ok that works, some questions though > > 1. Will there be binary distributions for 10.15 in the foreseeable future? No clue (I've been a bit out of the loop due to personal issues). Fink doesn't really own any computing resources. We've relied on developers with adequate machines to do the building, but it seems that nobody has been able to step up yet. > 2. So the fink command downloads the src pkg and compiles them, a > bit like gentoo, right? (For me this is just fine) Essentially, but see below. > 3. However the reason I have chosen fink over macports is that in my > understanding macports resolve dependencies rather poorly (for > example if you want to compile the latest GNU emacs master, it is > not obvious which packages you need. In the apt-get world you > would do > > sudo apt-get build-dep emacs > > does fink provide such a functionality? The closest similar function is "fink list -f --dotty-build <emacs>" This spits out an approximate package build tree in graphviz .dot format. > > 4. Apt-get has also auto-apt for backing your own debs > like > auto-apt run ./configure --prefix=/opt/emacs28 --with-x-toolkit=athena --without-pop --with-mailutils > make > make checkinstall and you are done. > > Anything similar in fink? The nearest analogue would be to copy a package's description (.info) and patch (.patch) files into a local directory (/opt/sw/fink/dists/local/main/finkinfo) and edit them as needed to change the build procedure. It was decided early on _not_ to provide a simple way for users to tweak the package builds. I'm not sure what went into that decision, as I wasn't with the project at the time, but it does make tech support easier if the expectation is that everybody's build is supposed to be identical on a given architecture. > Thanks > > Uwe Brauer > I hope the information that I provided was useful. --akh _______________________________________________ Fink-beginners mailing list [email protected] List archive: https://sourceforge.net/p/fink/mailman/fink-users/ Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-beginners