From: JD Robinson <jdrobi...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: Thoughts on sources
Date: Thu, 26 Mar 2015 01:20:20 -0700 (PDT) [thread overview]
Message-ID: <e1cf71a5-d489-4734-8ccd-6168aef928f6@googlegroups.com> (raw)
In-Reply-To: <44f693ab-1b07-4230-a02e-97c6f319624d@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
I thought so on the kernel modules.
I'll give those links a look, I'm trying to figure out how to come by the source from which a pre-existing binary package was compiled/packaged.
Not being in void very long, in apt/bed repositories it would have been a source repository and somepackage-version-src.deb ( or what have you for the extension ).
I haven't had time to experiment lately.
next prev parent reply other threads:[~2015-03-26 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 11:19 JD Robinson
2015-03-25 12:32 ` Stefan Mühlinghaus
2015-03-26 8:20 ` JD Robinson [this message]
2015-03-26 8:47 ` Juan RP
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e1cf71a5-d489-4734-8ccd-6168aef928f6@googlegroups.com \
--to="jdrobi..."@gmail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).