From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.182.111.168 with SMTP id ij8mr15140190obb.2.1427358022090; Thu, 26 Mar 2015 01:20:22 -0700 (PDT) X-BeenThere: voidlinux@googlegroups.com Received: by 10.140.95.68 with SMTP id h62ls605874qge.92.gmail; Thu, 26 Mar 2015 01:20:21 -0700 (PDT) X-Received: by 10.140.109.246 with SMTP id l109mr219626qgf.22.1427358021847; Thu, 26 Mar 2015 01:20:21 -0700 (PDT) Date: Thu, 26 Mar 2015 01:20:20 -0700 (PDT) From: JD Robinson To: voidlinux@googlegroups.com Message-Id: In-Reply-To: <44f693ab-1b07-4230-a02e-97c6f319624d@googlegroups.com> References: <40fad7e4-6ff4-46c4-b1ce-46ea5a9e1703@googlegroups.com> <44f693ab-1b07-4230-a02e-97c6f319624d@googlegroups.com> Subject: Re: Thoughts on sources MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1529_621986501.1427358020664" ------=_Part_1529_621986501.1427358020664 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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. ------=_Part_1529_621986501.1427358020664--