From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.68.190.232 with SMTP id gt8mr3807032pbc.3.1421983741171; Thu, 22 Jan 2015 19:29:01 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.182.75.227 with SMTP id f3ls394455obw.4.gmail; Thu, 22 Jan 2015 19:29:00 -0800 (PST) X-Received: by 10.182.46.234 with SMTP id y10mr40477obm.9.1421983740975; Thu, 22 Jan 2015 19:29:00 -0800 (PST) Date: Thu, 22 Jan 2015 19:29:00 -0800 (PST) From: Logen Kain To: voidlinux@googlegroups.com Message-Id: <865c1567-9403-4366-ab53-52d146021b44@googlegroups.com> In-Reply-To: <5a3573e6-4e06-4696-be3f-8c0ce562137b@googlegroups.com> References: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> <5a3573e6-4e06-4696-be3f-8c0ce562137b@googlegroups.com> Subject: Re: Few packaging questions MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_358_697287409.1421983740510" ------=_Part_358_697287409.1421983740510 Content-Type: multipart/alternative; boundary="----=_Part_359_491221384.1421983740510" ------=_Part_359_491221384.1421983740510 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit - *depends:* All the stuff required to run the package on the target system. Not needed at all on the building machine, and dependant on the target architecture. I have the issue of knowing what those dependancies actually are. Usually when I find lists from upstream they list everything needed to build which also happens to (usually) include the run-time depends as well. I'm just not sure how to easily seperate the run-time depends from the build dependancies. Most of what I know are simply things that i've learned over practice, such as .desktop files requireing desktop-file-utils to work properly. I would like the wiki page to be able to help people jump into package creation. My hope is that if people see a jump start guide, they will be more inclined to try and build packages and refernce our excellent manual when more detailed information is needed. Which I suppose means that the wiki needs to be a short and consise, perhaps even dirty, guide so people can get their toes a bit wet before diving into the full manual. Diving into a manual such as that is intemidating, even if it's important. Oh note to self: Add commit message standards for anyone intending to do a pull request as well as basic forking on github instructions. ------=_Part_359_491221384.1421983740510 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable


I have t= he issue of knowing what those dependancies actually are.  Usually whe= n I find lists from upstream they list everything needed to build which als= o happens to (usually) include the run-time depends as well.  I'm just= not sure how to easily seperate the run-time depends from the build depend= ancies.  Most of what I know are simply things that i've learned over = practice, such as .desktop files requireing desktop-file-utils to work prop= erly.

I would like the wiki page to be able to help people jump into = package creation.  My hope is that if people see a jump start guide, t= hey will be more inclined to try and build packages and refernce our excell= ent manual when more detailed information is needed.

Which I suppose = means that the wiki needs to be a short and consise, perhaps even dirty, gu= ide so people can get their toes a bit wet before diving into the full manu= al.  Diving into a manual such as that is intemidating, even if it's i= mportant.

Oh note to self: Add commit message standards for anyo= ne intending to do a pull request as well as basic forking on github instru= ctions.

------=_Part_359_491221384.1421983740510-- ------=_Part_358_697287409.1421983740510--