Void Linux discussion
 help / color / mirror / Atom feed
From: Logen Kain <walach.o...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: Few packaging questions
Date: Thu, 22 Jan 2015 19:29:00 -0800 (PST)	[thread overview]
Message-ID: <865c1567-9403-4366-ab53-52d146021b44@googlegroups.com> (raw)
In-Reply-To: <5a3573e6-4e06-4696-be3f-8c0ce562137b@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 1320 bytes --]


   
   - *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.

[-- Attachment #1.2: Type: text/html, Size: 1369 bytes --]

  reply	other threads:[~2015-01-23  3:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 20:51 Logen Kain
2015-01-22 23:21 ` Stefan Mühlinghaus
2015-01-23  3:29   ` Logen Kain [this message]
2015-02-02 19:09   ` Logen Kain
2015-01-23  9:13 ` Stefan Mühlinghaus
2015-02-02 19:05 ` Logen Kain
     [not found]   ` <CABLHwtef9mKadZZFR+06yNZhuOE8YS_Z_3FHE=xgZ9FUoX409Q@mail.gmail.com>
2015-02-02 19:14     ` Fwd: " Juan Romero Pardines
     [not found]     ` <CABLHwtfWdKPsexjP_p4oscok4US_y8gXWym1qGQ6uf7q7+COxw@mail.gmail.com>
2015-02-02 19:14       ` Juan Romero Pardines
2015-02-02 19:51         ` Logen Kain

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=865c1567-9403-4366-ab53-52d146021b44@googlegroups.com \
    --to="walach.o..."@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).