public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philipp Riegger <lists@anderedomain.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Building custom package for multi-arch/system
Date: Fri, 29 Jan 2010 00:23:14 +0100	[thread overview]
Message-ID: <20100129002314.55e1c093@jesper.s.riegger.name> (raw)
In-Reply-To: <20100128151741.GC4462@lady-voodoo.exosec.local>

On Thu, 28 Jan 2010 16:17:41 +0100
Beber <beber@meleeweb.net> wrote:

> So, I did a wrapper to emerge --buildpkg to create tbz2 with SHA1 in
> names function of USE, like : 
>   CHOST="x86_64-pc-linux-gnu"
>   ACCEPT_KEYWORDS="amd64"
>   tcpdump
> 
>   USE="+chroot +ipv6 -ssl -test -samba -smi"
>   is placed
> under /data/pkg/amd64/x86_64-pc-linux-gnu/net-analyzer/tcpdump-4.0.1_pre20090709+2bf4bfffad82d4ae519f76770b4f7db7b4416738.tbz2
> 
>   USE="+chroot +ipv6 +ssl -test +samba -smi"
>   is placed
> under /data/pkg/amd64/x86_64-pc-linux-gnu/net-analyzer/tcpdump-4.0.1_pre20090709+5e099e8337e4cadfceda6ccf4c881fbb495980bd.tbz2
> 

So these are the SHA1 sums of the packages? Nice.

I would like to see something like this:

With different CFLAGS, CHOST etc. the user should set a seperate PKGDIR.

USE-flags are encoded in the filename:

Sort USE-flags alphabetically, use a 1 for every enabled and a 0 for
every disabled USE-flag, make this array smaller using hex code ore
base64.

>   USE="+chroot +ipv6 -ssl -test -samba -smi"

110000

tcpdump-4.0.1_pre20090709+c0.tbz2

>   USE="+chroot +ipv6 +ssl -test +samba -smi"

111010

tcpdump-4.0.1_pre20090709+e2.tbz2

Problem with this is, if anything with the USEflags as we see it from
outside changes (USE-flags are added, deletes, renamed and therefore
change position), this gets none-unique, which can be fixed in several
ways.

Philipp



  parent reply	other threads:[~2010-01-29  0:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 15:17 [gentoo-dev] Building custom package for multi-arch/system Beber
2010-01-28 17:48 ` Jacob Godserv
2010-01-28 20:07 ` Gilles Dartiguelongue
2010-01-28 22:31 ` Robin H. Johnson
2010-01-29 10:52   ` Philipp Riegger
2010-01-29 21:44     ` Robin H. Johnson
2010-01-29 22:20       ` Zac Medico
2010-01-30 11:41   ` Bertrand Jacquin
2010-01-28 23:23 ` Philipp Riegger [this message]
2010-01-30 11:43   ` Bertrand Jacquin
2010-01-29  5:24 ` Max Arnold
2010-01-29  9:28   ` Antoni Grzymala
2010-01-30 11:59   ` Zac Medico
2010-01-30 15:13     ` Max Arnold
2010-01-30 16:20       ` Jacob Godserv
2010-01-30 18:11     ` [gentoo-dev] " Duncan
2010-01-30 21:24       ` Zac Medico

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=20100129002314.55e1c093@jesper.s.riegger.name \
    --to=lists@anderedomain.de \
    --cc=gentoo-dev@lists.gentoo.org \
    /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