Void Linux discussion
 help / color / mirror / Atom feed
From: polkovnik chechen <polkovn...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: xbps dependency tree?
Date: Wed, 21 Oct 2015 08:19:49 -0700 (PDT)	[thread overview]
Message-ID: <c09091ea-f3ff-4c2c-8a0a-daddae57ec9a@googlegroups.com> (raw)
In-Reply-To: <096ea552-038b-4c02-811c-ca92ceb6d715@googlegroups.com>

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

xlocate is looking out source site or other else?

21 Ekim 2015 Çarşamba 18:11:05 UTC+3 tarihinde Duncaen yazdı:
> Normally there is a list of dependencies somewhere in the software you 
> want to package, most times you can use xbps-query to find the -devel 
> package.
> If you dont know the dependencie name but you know the header files you 
> can use `xlocate` from `xtools` package to search for these header files in 
> packages.
> Am Mittwoch, 21. Oktober 2015 17:03:11 UTC+2 schrieb polkovnik chechen:
>> so when you are building a new package where are you find the 
>> dependencies (for new package-source) 
>> 21 Ekim 2015 Çarşamba 16:32:30 UTC+3 tarihinde polkovnik chechen yazdı:
>>> i wonder how xbps is looking for dependencies.how the system is 
>>> working.what are the diffrences from arch,ubuntu or others.ex where do you 
>>> know a package's dependencies?when are you building a package how do you 
>>> know?

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

  reply	other threads:[~2015-10-21 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 13:32 polkovnik chechen
2015-10-21 14:14 ` Duncaen
2015-10-21 15:06   ` polkovnik chechen
2015-10-21 15:03 ` polkovnik chechen
2015-10-21 15:11   ` Duncaen
2015-10-21 15:19     ` polkovnik chechen [this message]
2015-10-21 15:21       ` Duncaen
2015-10-21 15:25         ` polkovnik chechen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c09091ea-f3ff-4c2c-8a0a-daddae57ec9a@googlegroups.com \
    --to="polkovn..."@gmail.com \
    --cc="void..."@googlegroups.com \


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