Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #231209
| From | <tomas@tuxteam.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: URL to source file |
| Date | 2021-01-27 11:30 +0100 |
| Message-ID | <BBQfg-3qe-13@gated-at.bofh.it> (permalink) |
| References | <BBPjb-2RD-1@gated-at.bofh.it> <BBPsS-2UQ-9@gated-at.bofh.it> <BBPMd-31u-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Wed, Jan 27, 2021 at 10:49:49AM +0100, Emanuel Berg wrote: > tomas wrote: > > > https://sources.debian.org/src/units/2.18-1/definitions.units > > It is still in some interface but good enough for a reference. > > Good enough for government work! :-) > So it is: https://sources.debian.org/src/ + package name + > package version... so far, so good (but see below for gotchas) ... > ... + file name ... now this is more complicated. Note that you are looking at a source package. Sometimes, the file gets just "copied over" to somewhere else, as in your current case. Source and destination paths... well. Look into the package's Makefiles and into the debian subdir. Long story :-) Sometimes, though, it's a .c file, which gets trampled on by a stampede of compilers and linkers. Bits of its soul end up scattered in various places of /usr/bin and/or /usr/lib. Even the part with the package name is an oversimplification. Many times, one source package gives birth to several binary packages (e.g. a set of libraries usable by other packages plus a set of basic binary utilities which go with those libraries). But if you keep those caveats in mind, the above is a good start. Cheers - t
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
URL to source file Emanuel Berg <moasenwood@zoho.eu> - 2021-01-27 10:30 +0100
Re: URL to source file <tomas@tuxteam.de> - 2021-01-27 10:40 +0100
Re: URL to source file Emanuel Berg <moasenwood@zoho.eu> - 2021-01-27 11:00 +0100
Re: URL to source file Emanuel Berg <moasenwood@zoho.eu> - 2021-01-27 11:10 +0100
Re: URL to source file Emanuel Berg <moasenwood@zoho.eu> - 2021-01-27 11:20 +0100
Re: URL to source file Emanuel Berg <moasenwood@zoho.eu> - 2021-01-27 11:50 +0100
Re: URL to source file Emanuel Berg <moasenwood@zoho.eu> - 2021-01-27 12:10 +0100
Re: URL to source file Vincent Lefevre <vincent@vinc17.net> - 2021-01-27 12:40 +0100
Re: URL to source file Emanuel Berg <moasenwood@zoho.eu> - 2021-01-27 14:50 +0100
Re: URL to source file Vincent Lefevre <vincent@vinc17.net> - 2021-01-28 02:30 +0100
Re: URL to source file Greg Wooledge <wooledg@eeg.ccf.org> - 2021-01-28 14:20 +0100
Re: URL to source file Vincent Lefevre <vincent@vinc17.net> - 2021-01-28 15:40 +0100
Re: URL to source file Emanuel Berg <moasenwood@zoho.eu> - 2021-01-29 05:00 +0100
Re: URL to source file Andrei POPESCU <andreimpopescu@gmail.com> - 2021-01-27 17:10 +0100
Re: URL to source file <tomas@tuxteam.de> - 2021-01-27 11:30 +0100
Re: URL to source file Stefan Monnier <monnier@iro.umontreal.ca> - 2021-01-27 16:00 +0100
Re: URL to source file Emanuel Berg <moasenwood@zoho.eu> - 2021-01-27 16:20 +0100
Re: URL to source file Emanuel Berg <moasenwood@zoho.eu> - 2021-01-27 16:30 +0100
csiph-web