From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.52.6.161 with SMTP id c1mr2540379vda.5.1421959862689; Thu, 22 Jan 2015 12:51:02 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.182.227.166 with SMTP id sb6ls352446obc.3.gmail; Thu, 22 Jan 2015 12:51:02 -0800 (PST) X-Received: by 10.182.230.133 with SMTP id sy5mr29692obc.1.1421959862442; Thu, 22 Jan 2015 12:51:02 -0800 (PST) Date: Thu, 22 Jan 2015 12:51:01 -0800 (PST) From: Logen Kain To: voidlinux@googlegroups.com Message-Id: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> Subject: Few packaging questions MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1307_1508034283.1421959861957" ------=_Part_1307_1508034283.1421959861957 Content-Type: multipart/alternative; boundary="----=_Part_1308_930192487.1421959861957" ------=_Part_1308_930192487.1421959861957 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If I have more dependencies listed than I actually need, what is the easiest way to check? Where is the easiest place to see the list of packages that don't need to be explicitly declared? Which, if I understand correctly, should be all the bootstrap packages. I would like to add a Packaging 101 to the wiki where I explain quick and dirty ways to get a package running. My typical method: - Add the make jobs to my ./etc/conf - Find source I want to package. - Look at list of depends if the dev has it readily available. - Find the equivalent void packages that have those depends. If the depends have a 32bit version, add it to target, if not, add it to host - Add them to a template along with all the basic information. - Tell xbps to install - grab the checksum from hostdir, add it to the template, and run again. -- Can also download the file separately but I prefer to do it this way for consistency - Notice any config errors and add more dependencies. Keep going about it that way till it builds, if there are other strange errors I take a look at the AUR to see if they patch it. At that point I'll either make a patch or try to run a GIT version. If I have any questions I consult the Manual religiously. If I still can't figure it out I'd post to google+, thankfully now people are using this forum so I can post here. As for the "depends" line, I'm also not sure how to figure out everything a package depends on. If I check the dependencies on package foo after I build it, and I haven't added any depends, will it still list the depends I need to add to the template? Or does xbps-query get it's depends information from the built package? I'd like to refine my process here with knowledge from the community before doing a write up on the wiki. Things that I'd like to add to the wiki: - my process, as noted above - an example of each build style with explanations - an example without a build style - How to install a custom built package If you've gotten this far, thanks for taking the time and I hope I can get some new insight on how I suck at packaging ^_^ ------=_Part_1308_930192487.1421959861957 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

If I have more dependencies listed than I actually need, what is the easiest way to check?
Where is the easiest place to see the list of packages that don't need to be explicitly declared?  Which, if I understand correctly, should be all the bootstrap packages.

I would like to add a Packaging 101 to the wiki where I explain quick and dirty ways to get a package running.

My typical method:

Keep going about it that way till it builds, if there are other strange errors I take a look at the AUR to see if they patch it.  At that point I'll either make a patch or try to run a GIT version.

If I have any questions I consult the Manual religiously.  If I still can't figure it out I'd post to google+, thankfully now people are using this forum so I can post here.

As for the "depends" line, I'm also not sure how to figure out everything a package depends on.  If I check the dependencies on package foo after I build it, and I haven't added any depends, will it still list the depends I need to add to the template?  Or does xbps-query get it's depends information from the built package?

I'd like to refine my process here with knowledge from the community before doing a write up on the wiki.

Things that I'd like to add to the wiki:

If you've gotten this far, thanks for taking the time and I hope I can get some new insight on how I suck at packaging ^_^


------=_Part_1308_930192487.1421959861957-- ------=_Part_1307_1508034283.1421959861957-- From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.236.47.137 with SMTP id t9mr3139278yhb.43.1421968872310; Thu, 22 Jan 2015 15:21:12 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.140.21.175 with SMTP id 44ls825512qgl.99.gmail; Thu, 22 Jan 2015 15:21:12 -0800 (PST) X-Received: by 10.140.31.134 with SMTP id f6mr39820qgf.33.1421968872124; Thu, 22 Jan 2015 15:21:12 -0800 (PST) Date: Thu, 22 Jan 2015 15:21:11 -0800 (PST) From: =?UTF-8?Q?Stefan_M=C3=BChlinghaus?= To: voidlinux@googlegroups.com Message-Id: <5a3573e6-4e06-4696-be3f-8c0ce562137b@googlegroups.com> In-Reply-To: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> References: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> Subject: Re: Few packaging questions MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_981_1952996705.1421968871828" ------=_Part_981_1952996705.1421968871828 Content-Type: multipart/alternative; boundary="----=_Part_982_1775092243.1421968871833" ------=_Part_982_1775092243.1421968871833 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yes, a packing howto would be interesting, especially dependency resolution. My current approach is working so far, but I'm wondering if it could not be streamlined. Are there any void-tools that support manual dependency resolution? Also I don't think I understand your reasoning of what to add to which "depends"-variable. Maybe I'm misunderstanding you, but this is how I divide them: - *hostmakedepends:* All the stuff that the building machine needs to be able to run through the building process. Mostly tools, like pkg-config or somesuch. This is needed regardless of which architecture you are building for. - *makedepends:* All stuff that is needed du build the package on the building machine. Usually devel-versions of the required libraries. This is dependant on the architecture you are building for. - *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'm probably stating something obvious here, but there you go :) ------=_Part_982_1775092243.1421968871833 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Yes, a packing howto would be interesting, especially depe= ndency resolution. My current approach is working so far, but I'm wondering= if it could not be streamlined. Are there any void-tools that support manu= al dependency resolution?

Also I don't think I understan= d your reasoning of what to add to which "depends"-variable. Maybe I'm misu= nderstanding you, but this is how I divide them:

<= ul>
  • hostmakedepends: All the stuff that the building machine need= s to be able to run through the building process. Mostly tools, like pkg-co= nfig or somesuch. This is needed regardless of which architecture you are b= uilding for.
  • makedepends: All stuff that is needed du bu= ild the package on the building machine. Usually devel-versions of the requ= ired libraries. This is dependant on the architecture you are building for.=
  • depends: All the stuff required to run the package on t= he target system. Not needed at all on the building machine, and dependant = on the target architecture.

    • I'm prob= ably stating something obvious here, but there you go :)
    ------=_Part_982_1775092243.1421968871833-- ------=_Part_981_1952996705.1421968871828-- 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
    • depends: All the stuff required to run the = package on the target system. Not needed at all on the building machine, an= d dependant on the target architecture.


    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-- From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.182.168.114 with SMTP id zv18mr4956730obb.3.1422004436751; Fri, 23 Jan 2015 01:13:56 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.140.97.247 with SMTP id m110ls957435qge.81.gmail; Fri, 23 Jan 2015 01:13:56 -0800 (PST) X-Received: by 10.140.81.199 with SMTP id f65mr1019qgd.12.1422004436611; Fri, 23 Jan 2015 01:13:56 -0800 (PST) Date: Fri, 23 Jan 2015 01:13:56 -0800 (PST) From: =?UTF-8?Q?Stefan_M=C3=BChlinghaus?= To: voidlinux@googlegroups.com Message-Id: <8e3b9681-be92-46f6-9298-86ada0a1cfdf@googlegroups.com> In-Reply-To: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> References: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> Subject: Re: Few packaging questions MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1223_697816925.1422004436284" ------=_Part_1223_697816925.1422004436284 Content-Type: multipart/alternative; boundary="----=_Part_1224_1811114107.1422004436290" ------=_Part_1224_1811114107.1422004436290 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ah, I see what you mean. Regarding runtime dependencies void is very forthcoming since it usually automatically detects them and you will not have to specify anything. You only need to add what cannot be detected automatically, and that boils down to the infos from the softwares author and what you can discern yourself by testing. I don't think that part can be significantly simplified since the possible ways one package can depend on another are so diverse. I would gladly be proven wrong though ;) ------=_Part_1224_1811114107.1422004436290 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
    Ah, I see what you mean. Regarding runtime dependencies void is very forthcoming since it usually automatically detects them and you will not have to specify anything. You only need to add what cannot be detected automatically, and that boils down to the infos from the softwares author and what you can discern yourself by testing. I don't think that part can be significantly simplified since the possible ways one package can depend on another are so diverse. I would gladly be proven wrong though ;)
    ------=_Part_1224_1811114107.1422004436290-- ------=_Part_1223_697816925.1422004436284-- From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.50.23.75 with SMTP id k11mr10926738igf.3.1422903937102; Mon, 02 Feb 2015 11:05:37 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.182.60.168 with SMTP id i8ls1115778obr.20.gmail; Mon, 02 Feb 2015 11:05:36 -0800 (PST) X-Received: by 10.182.33.38 with SMTP id o6mr125349obi.16.1422903936715; Mon, 02 Feb 2015 11:05:36 -0800 (PST) Date: Mon, 2 Feb 2015 11:05:36 -0800 (PST) From: Logen Kain To: voidlinux@googlegroups.com Message-Id: <0c0e2209-88d4-4871-bfab-97cad711ff53@googlegroups.com> In-Reply-To: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> References: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> Subject: Re: Few packaging questions MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2979_46652837.1422903936342" ------=_Part_2979_46652837.1422903936342 Content-Type: multipart/alternative; boundary="----=_Part_2980_262700304.1422903936342" ------=_Part_2980_262700304.1422903936342 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit When it comes to installing home built packages, I typically do one of these: xbps-install -R /path/to/binpkgs foo Is there a way to simply install a package without a repository? I didn't notice anything in the man page. To clarify: In Archlinux, if I remember correctly, "pacman -u /path/to/package" Will install the package without the need for repo data. ------=_Part_2980_262700304.1422903936342 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
    When it comes to installing home built packages, I typically do one of these:
    xbps-install -R /path/to/binpkgs foo

    Is there a way to simply install a package without a repository?  I didn't notice anything in the man page.

    To clarify:
    In Archlinux, if I remember correctly, "pacman -u /path/to/package" Will install the package without the need for repo data.
    ------=_Part_2980_262700304.1422903936342-- ------=_Part_2979_46652837.1422903936342-- From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.68.241.163 with SMTP id wj3mr18236929pbc.8.1422904178545; Mon, 02 Feb 2015 11:09:38 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.182.237.80 with SMTP id va16ls76932obc.60.gmail; Mon, 02 Feb 2015 11:09:38 -0800 (PST) X-Received: by 10.182.107.228 with SMTP id hf4mr126736obb.6.1422904178341; Mon, 02 Feb 2015 11:09:38 -0800 (PST) Date: Mon, 2 Feb 2015 11:09:37 -0800 (PST) From: Logen Kain To: voidlinux@googlegroups.com Message-Id: 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_370_812446470.1422904177951" ------=_Part_370_812446470.1422904177951 Content-Type: multipart/alternative; boundary="----=_Part_371_1086793664.1422904177951" ------=_Part_371_1086793664.1422904177951 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > > > - *hostmakedepends:* All the stuff that the building machine needs to > be able to run through the building process. Mostly tools, like pkg-config > or somesuch. This is needed regardless of which architecture you are > building for. > - *makedepends:* All stuff that is needed du build the package on the > building machine. Usually devel-versions of the required libraries. This is > dependant on the architecture you are building for. > - *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 just realized I never clarified myself here, my bad. The way I look at it: - *hostmakedepends: *Depends that are not architecture specific. - *makedepends:* Depends that *are* architecture specific. - So I check if 32-bit packages exist. If they do, I know it's architecture specific. - *depends: *Same as what you said, which actually helped clarify it a bit for me. ------=_Part_371_1086793664.1422904177951 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
    • hostmakedepends: All the stuff that the = building machine needs to be able to run through the building process. Most= ly tools, like pkg-config or somesuch. This is needed regardless of which a= rchitecture you are building for.
    • makedepends: All stuff= that is needed du build the package on the building machine. Usually devel= -versions of the required libraries. This is dependant on the architecture = you are building for.
    • depends: All the stuff required to= run the package on the target system. Not needed at all on the building ma= chine, and dependant on the target architecture.

    I just realized I never clar= ified myself here, my bad.

    The way I look at it:
    • hostm= akedepends: Depends that are not architecture specific.
    • make= depends: Depends that are architecture specific. - So I check if= 32-bit packages exist.  If they do, I know it's architecture specific= .
    • depends: Same as what you said, which actually helped clar= ify it a bit for me.
    ------=_Part_371_1086793664.1422904177951-- ------=_Part_370_812446470.1422904177951-- From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.43.91.68 with SMTP id bl4mr18754529icc.17.1422904464284; Mon, 02 Feb 2015 11:14:24 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.50.88.5 with SMTP id bc5ls1415786igb.0.gmail; Mon, 02 Feb 2015 11:14:24 -0800 (PST) X-Received: by 10.42.62.203 with SMTP id z11mr19293145ich.9.1422904464163; Mon, 02 Feb 2015 11:14:24 -0800 (PST) Return-Path: Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com. [2607:f8b0:4001:c05::229]) by gmr-mx.google.com with ESMTPS id jn10si1043471igb.3.2015.02.02.11.14.24 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Feb 2015 11:14:24 -0800 (PST) Received-SPF: pass (google.com: domain of xtr...@gmail.com designates 2607:f8b0:4001:c05::229 as permitted sender) client-ip=2607:f8b0:4001:c05::229; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of xtr...@gmail.com designates 2607:f8b0:4001:c05::229 as permitted sender) smtp.mail=xtr...@gmail.com; dkim=pass head...@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Received: by mail-ig0-f169.google.com with SMTP id hl2so19321858igb.0 for ; Mon, 02 Feb 2015 11:14:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=DiB0/jOKcyuOjYOm+azVQA5fxWZfDdHmwcLqwn4Dx2A=; b=07AUex7vpI+tHqhET1zEj/orpYJUa/AQiWhTwHzW/YUEGihfOoEqnD1blh+YH80jCX 0pw65YovKqsJgq2NMMd0AJgJS1M+YKlfyBwNnceUoz9dV9/xey4Hy4EDfFMaVyPtM9YX GjVFAQp7U6dAEZwe0GL9sRjxhQGT5j9bfi1wVO5l6mkQJhal0yXu3m6Y5NbWZBwcsYlU ZeOM6OfP9dCufSKQVmVQ8ey7zSC5pUxbK3GyvNfxdtc9AGT3we3ifBQGAjWz0zC7/f45 FU90dcHz4UsoJPxE830hl3sMHmraanWHV2jwpY+p41kSfk1vZ3+wnPcQLW1VkQ9yT2a1 mLRw== X-Received: by 10.107.130.40 with SMTP id e40mr13434222iod.49.1422904464058; Mon, 02 Feb 2015 11:14:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.207.2 with HTTP; Mon, 2 Feb 2015 11:14:03 -0800 (PST) In-Reply-To: References: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> <0c0e2209-88d4-4871-bfab-97cad711ff53@googlegroups.com> From: Juan Romero Pardines Date: Mon, 2 Feb 2015 20:14:03 +0100 Message-ID: Subject: Fwd: Few packaging questions To: voidlinux@googlegroups.com Content-Type: multipart/alternative; boundary=001a113ecd4a21302b050e1fc33e --001a113ecd4a21302b050e1fc33e Content-Type: text/plain; charset=UTF-8 No, there's no way of installing pkgs without repos. xbps has been designed to require a repository to store packages, the reason is that this is the way to check its sha256 hash (for local repos) among others. --001a113ecd4a21302b050e1fc33e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
    No, = there's no way of installing pkgs without repos.

    xbps has = been designed to require a repository to store packages, the reason is that= this
    is the way to check its sha256 hash (for local repos) among = others.

    --001a113ecd4a21302b050e1fc33e-- From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.182.241.71 with SMTP id wg7mr19277185obc.38.1422904496732; Mon, 02 Feb 2015 11:14:56 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.182.210.231 with SMTP id mx7ls997008obc.36.gmail; Mon, 02 Feb 2015 11:14:56 -0800 (PST) X-Received: by 10.182.126.47 with SMTP id mv15mr7010712obb.18.1422904496591; Mon, 02 Feb 2015 11:14:56 -0800 (PST) Return-Path: Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com. [2607:f8b0:4001:c03::235]) by gmr-mx.google.com with ESMTPS id n1si1064565igp.0.2015.02.02.11.14.56 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Feb 2015 11:14:56 -0800 (PST) Received-SPF: pass (google.com: domain of xtr...@gmail.com designates 2607:f8b0:4001:c03::235 as permitted sender) client-ip=2607:f8b0:4001:c03::235; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of xtr...@gmail.com designates 2607:f8b0:4001:c03::235 as permitted sender) smtp.mail=xtr...@gmail.com; dkim=pass head...@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Received: by mail-ie0-x235.google.com with SMTP id rd18so10587738iec.12 for ; Mon, 02 Feb 2015 11:14:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=KNgzNcc9yDpASXSoAMyhz8F6Xa9DAz8RloGYb5MaI6Y=; b=PBvQsAkQBJWOHAj8P9xrf6OSSCB9Bwc8vhlYyPnEZzvVEDAEkGNZZ+neOCJ5Mlt+FL L3aXp00eM3SURQKEOKAbsZ/T9QJw3WCQzjjam7P4TKVxRBzo50VvBARCTquKj6i5fa22 RANbSlGBmv/lGykraBSCiIZcfwMfWC9rEf4P9JnNqOHog9ugx81/v6GJWlN/EICxZJoq 0GnN9I1IzWrwZJ84SQpiAZ6MofcbDQt4Vox4c6EO8kfnu5lH+ipcEHmJZgsg4D8mwmSi DJB3OSGnOpF1FqBao9GOyPuv/zRjQRDRWt8qPlP9hwyX8yMZGO9QvUWzIF5T7vRhp0jd jFEw== X-Received: by 10.43.6.71 with SMTP id oj7mr21000254icb.87.1422904496456; Mon, 02 Feb 2015 11:14:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.207.2 with HTTP; Mon, 2 Feb 2015 11:14:36 -0800 (PST) In-Reply-To: References: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> <0c0e2209-88d4-4871-bfab-97cad711ff53@googlegroups.com> From: Juan Romero Pardines Date: Mon, 2 Feb 2015 20:14:36 +0100 Message-ID: Subject: Fwd: Few packaging questions To: voidlinux@googlegroups.com Content-Type: multipart/alternative; boundary=bcaec5158d910f9496050e1fc5f8 --bcaec5158d910f9496050e1fc5f8 Content-Type: text/plain; charset=UTF-8 If you don't want to specify -R/--repository each time, just can just declare that repo in a xbps configuration file (as explained in xbps.d(5)): $ echo repository=/path/to/hostdir/binpkgs > /etc/xbps.d/my-local-repo.conf --bcaec5158d910f9496050e1fc5f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
    If you do= n't want to specify -R/--repository each time, just can just declare th= at
    repo in a xbps configuration file (as explained in xbps.d(5)):
    $ echo repository=3D/path/to/hostdir/binpkgs > /etc/xbps.d/my-loc= al-repo.conf

    --bcaec5158d910f9496050e1fc5f8-- From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.236.40.8 with SMTP id e8mr18460606yhb.41.1422906672715; Mon, 02 Feb 2015 11:51:12 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.182.108.228 with SMTP id hn4ls1082035obb.80.gmail; Mon, 02 Feb 2015 11:51:12 -0800 (PST) X-Received: by 10.182.46.234 with SMTP id y10mr128850obm.9.1422906672556; Mon, 02 Feb 2015 11:51:12 -0800 (PST) Date: Mon, 2 Feb 2015 11:51:12 -0800 (PST) From: Logen Kain To: voidlinux@googlegroups.com Message-Id: <92a5f7af-9b95-42fe-90cb-dad466e18206@googlegroups.com> In-Reply-To: References: <3dc50f24-8562-4acd-b23c-632ad013bf8c@googlegroups.com> <0c0e2209-88d4-4871-bfab-97cad711ff53@googlegroups.com> Subject: Re: Few packaging questions MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_3208_1557422190.1422906672163" ------=_Part_3208_1557422190.1422906672163 Content-Type: multipart/alternative; boundary="----=_Part_3209_2064057694.1422906672163" ------=_Part_3209_2064057694.1422906672163 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Oh I don't mind typing it in every time, I use fish so it's painless anyway. I was mostly interested in package portability. I was guessing it was probably designed that way. Thanks. ------=_Part_3209_2064057694.1422906672163 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
    Oh I don't mind typing it in every time, I use fish so it's painless anyway.  I was mostly interested in package portability.  I was guessing it was probably designed that way.  Thanks.
    ------=_Part_3209_2064057694.1422906672163-- ------=_Part_3208_1557422190.1422906672163--