[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-util/lockrun: metadata.xml ChangeLog lockrun-2.ebuild Manifest

2008-02-06 Thread Donnie Berkholz
On 18:22 Tue 05 Feb , Caleb Tennis (caleb) wrote:
> 1.1  dev-util/lockrun/lockrun-2.ebuild
> 
> file : 
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-util/lockrun/lockrun-2.ebuild?rev=1.1&view=markup
> plain: 
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-util/lockrun/lockrun-2.ebuild?rev=1.1&content-type=text/plain

> src_unpack() {
>   cp "${FILESDIR}"/lockrun.c "${S}"/lockrun.c
> }

It would be nice to version this, bzip it and stick it on a mirror, and 
even nicer yet to get upstream to do that.

> 
> src_compile() {
>   $(tc-getCC) ${CFLAGS} lockrun.c -o lockrun
> }
> 
> src_install () {
>   dodir /usr/bin
>   cp lockrun "${D}"/usr/bin

dobin?

Thanks,
Donnie
-- 
gentoo-dev@lists.gentoo.org mailing list



[gentoo-dev] retiring + looking maintainers for sendmail, tenshi, scapy, ftester

2008-02-06 Thread Andrea Barisani

Hi folks, I'm retiring.

I was maintaining the following packages:

app-admin/tenshi (note: I'm upstream as well)
mail-mta/sendmail
net-analyzer/scapy
net-analyzer/ftester (note: I'm upstream as well)

So those needs new maintainership.

Cheers

-- 
Andrea Barisani <[EMAIL PROTECTED]>.*.
Gentoo Linux Infrastructure Developer  V
 (   )
PGP-Key 0x864C9B9E http://dev.gentoo.org/~lcars/pubkey.asc   (   )
0A76 074A 02CD E989 CE7F AC3F DA47 578E 864C 9B9E^^_^^
  "Pluralitas non est ponenda sine necessitate"
-- 
gentoo-dev@lists.gentoo.org mailing list



Re: [gentoo-dev] VDB access

2008-02-06 Thread Michael Haubenwallner
On Wed, 2008-02-06 at 07:30 +0100, Vlastimil Babka wrote:
> Zac Medico wrote:

> or we would want to use the general metadata query also for other
> purposes.

> Anyway, restricting ebuilds from vdb access sounds like a good idea to me.

+1 for general metadata query interface.

In prefix (specifically on AIX) we have some nasty requirement to merge
object files inside archive files, because shared-objects should be
members of a static libraries, fex libstdc++.so.6 is an archive member
of libstdc++.a.

This (still experimental) inside-library-merge currently is done using
some hackery in profile.bashrc, but this requires access to vdb/CONTENTS
in pre_pkg_postrm() to clean up after unmerge.

/haubi/
-- 
Michael Haubenwallner
Gentoo on a different level

-- 
gentoo-dev@lists.gentoo.org mailing list



Re: [gentoo-dev] How to get more involved?

2008-02-06 Thread Denis Dupeyron
On Feb 5, 2008 11:49 PM, William L. Thomson Jr. <[EMAIL PROTECTED]> wrote:
>
> On Sat, 2008-02-02 at 08:54 +0100, Luca Barbato wrote:
> > William L. Thomson Jr. wrote:
> > > http://www.gentoo.org/proj/en/java/getting-involved.xml
> > >
> > Maybe could we get it moved on the top level?
>
> Sure, there is some Java specific stuff in there. Likely need to remove
> that first, but is a pretty general doc.

You may want to mix in some of what's in there:
http://dev.gentoo.org/~calchan/howtohelp.txt

It's my usual answer to requests we get on the recruiters' list. I
thought that might help.

Denis.
-- 
gentoo-dev@lists.gentoo.org mailing list



Re: [gentoo-dev] Re: VDB access

2008-02-06 Thread Ciaran McCreesh
On Wed, 06 Feb 2008 08:43:20 +0200
Petteri Räty <[EMAIL PROTECTED]> wrote:
> Ciaran McCreesh kirjoitti:
> > Incidentally, if anyone is still thinking that built_with_use is
> > fine... It doesn't handle IUSE defaults, which means package
> > managers have to store a hacked version of IUSE in VDB for EAPI 1.
> > This isn't documented anywhere and is highly unobvious.
> 
> I don't understand this. IUSE defaults affect whether a use flag is
> on or off when installing the ebuild. Why would it need to be stored
> in the VDB? There should only be a need of the value of $USE. Please
> elaborate.

VDB stores exact copies of ebuild metadata variables, except for IUSE.
IUSE is the only one that gets modified by the package manager.

-- 
Ciaran McCreesh


signature.asc
Description: PGP signature


Re: [gentoo-dev] VDB access

2008-02-06 Thread Ciaran McCreesh
On Tue, 05 Feb 2008 13:21:34 -0800
Zac Medico <[EMAIL PROTECTED]> wrote:
> > * Allow package managers that implement native_built_with_use to
> > sandbox off vdb completely, and ban all ebuild access to vdb.
> 
> The problem that I see with native_built_with_use is that the
> package manager will then need to precisely implement the
> build_with_use interface along with any and all supported options
> (and this interface would effectively become part of the EAPI).

True.

> If the package manager exposes a slightly lower level interface to
> the USE flags then build_with_use can use that instead, and the
> package manager won't have to implement the full build_with_use
> interface.  For example, portageq currently supports a "metadata"
> command that can be used to query installed package metadata such as
> USE and IUSE. Perhaps we should use some type of interface similar
> to that.

That's also a possibility. How about something like:

if [[ -n "${E_INSTALLED_PKG_METADATA_CMD}" ]] ; then
${E_INSTALLED_PKG_METADATA_CMD} >=cat/pkg-1.23 USE foo
else
# old vdb stuff
fi

with heavy (and checked) restrictions upon legal metadata keys (stuff
that's in individual files, not environment.bz2)?

-- 
Ciaran McCreesh


signature.asc
Description: PGP signature


Re: [gentoo-dev] VDB access

2008-02-06 Thread Ciaran McCreesh
On Wed, 06 Feb 2008 14:24:28 +0100
Michael Haubenwallner <[EMAIL PROTECTED]> wrote:
> +1 for general metadata query interface.
> 
> In prefix (specifically on AIX) we have some nasty requirement to
> merge object files inside archive files, because shared-objects
> should be members of a static libraries, fex libstdc++.so.6 is an
> archive member of libstdc++.a.
> 
> This (still experimental) inside-library-merge currently is done using
> some hackery in profile.bashrc, but this requires access to
> vdb/CONTENTS in pre_pkg_postrm() to clean up after unmerge.

CONTENTS isn't metadata in the conventional sense... If someone's
redesigning VDB, they're very unlikely to keep CONTENTS in the same
format. So you'd need a second, different interface for that...

-- 
Ciaran McCreesh


signature.asc
Description: PGP signature


Re: [gentoo-dev] retiring + looking maintainers for sendmail, tenshi, scapy, ftester

2008-02-06 Thread Mike Auty

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sorry to see you leave,
I can maintain scapy if no one else wants to?
Mike  5:)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHqglzu7rWomwgFXoRAismAJ4+4D50v0k6VSRfEfRV4mMiBP9QHACeLHJB
1IYpKEqzWFsdiFYXG7IJyhc=
=16SE
-END PGP SIGNATURE-
--
gentoo-dev@lists.gentoo.org mailing list



Re: [gentoo-dev] How to get more involved?

2008-02-06 Thread Josh Nichols

Denis Dupeyron wrote:

On Feb 5, 2008 11:49 PM, William L. Thomson Jr. <[EMAIL PROTECTED]> wrote:
  

On Sat, 2008-02-02 at 08:54 +0100, Luca Barbato wrote:


William L. Thomson Jr. wrote:
  

http://www.gentoo.org/proj/en/java/getting-involved.xml



Maybe could we get it moved on the top level?
  

Sure, there is some Java specific stuff in there. Likely need to remove
that first, but is a pretty general doc.



You may want to mix in some of what's in there:
http://dev.gentoo.org/~calchan/howtohelp.txt

It's my usual answer to requests we get on the recruiters' list. I
thought that might help.

Denis.
  

User Relations also has a blurb on this topic on their project page:

http://www.gentoo.org/proj/en/userrel/index.xml#doc_chap5
--
gentoo-dev@lists.gentoo.org mailing list



[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: depend.apache.eclass

2008-02-06 Thread Donnie Berkholz
On 21:20 Wed 06 Feb , Benedikt Boehm (hollow) wrote:
> Revision  ChangesPath
> 1.42 eclass/depend.apache.eclass
> 
> file : 
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/depend.apache.eclass?rev=1.42&view=markup
> plain: 
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/depend.apache.eclass?rev=1.42&content-type=text/plain
> diff : 
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/depend.apache.eclass?r1=1.41&r2=1.42

> +check_apache_threads_in() {

"check_" is a really poor function prefix, because it doesn't tell you 
whether it returns success for when threads exist or returns success for 
when it's unthreaded. Rename this something like "has_apache_threads" 
instead.

> + debug-print-function $FUNCNAME $*
> +
> + if ! built_with_use www-servers/apache threads ; then
> + return
> + fi
> +
> + local myforeign="$1"
> + local myflag="${2:-threads}"
> +
> + if ! built_with_use ${myforeign} ${myflag} ; then
> + echo
> + eerror "You need to enable USE flag '${myflag}' in ${myforeign} 
> to"
> + eerror "build a thread-safe version of ${CATEGORY}/${PN} for 
> use"
> + eerror "with www-servers/apache"
> + die "Need missing USE flag '${myflag}' in ${myforeign}"
> + fi
> +}

Thanks,
Donnie
-- 
gentoo-dev@lists.gentoo.org mailing list



Re: [gentoo-dev] new portage categories

2008-02-06 Thread Alec Warner
On 2/4/08, Jonas Bernoulli <[EMAIL PROTECTED]> wrote:
> On 2/4/08, Donnie Berkholz <[EMAIL PROTECTED]> wrote:
> > On 20:11 Mon 04 Feb , Jonas Bernoulli wrote:
> > > Thinking about it again I would say tags and categories just fulfill
> > > different purposes. Tags can not replace categories but might be a
> > > useful extension to categories for the tasks I described, not more not
> > > less. They are not better or worse, just different:)
> >
> > Why don't you think they can replace categories?
>
> Quick answer: Because there are packages with the same name in
> different categories. How would tags deal with that?

Techincally you could enforce UNIQUE(pkg,[tags]), I agree thats a poor
constraint though ;)

>
> Long answer: Well maybe there is a way. But I think that it would
> probably take a long time to make such a change. Technically tags
> could probably replace categories but then their would be no definite
> "full" name for that package anymore.
>
> Someone calls it foo/app and someone bar/app, and since there is also
> fuu/app which is a different application but with the same name,
> nobody would no for sure about package is being taked about without
> checking if his beloved foo/app is the same as bar/app the other guy
> is talking about. Also how do you sort the packages in the tree? all
> in one directory?! every package in the directories of each tag it
> belongs to using hardlinks?

Filtering packages on tags would be very difficult without a metadata
cache for metadata XML as you would need to pull down each package's
metadata.xml to determine if it meets your filtering requirements.
Excluding individual packages wouldn't be that hard although I imagine
there may be problems with the length of the rsync command line if
your filtering is too aggressive ;)

>
> -- Jonas
> --
> gentoo-dev@lists.gentoo.org mailing list
>
>
-- 
gentoo-dev@lists.gentoo.org mailing list



Re: [gentoo-dev] VDB access

2008-02-06 Thread Zac Medico
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ciaran McCreesh wrote:
> On Tue, 05 Feb 2008 13:21:34 -0800
> Zac Medico <[EMAIL PROTECTED]> wrote:
>> If the package manager exposes a slightly lower level interface to
>> the USE flags then build_with_use can use that instead, and the
>> package manager won't have to implement the full build_with_use
>> interface.  For example, portageq currently supports a "metadata"
>> command that can be used to query installed package metadata such as
>> USE and IUSE. Perhaps we should use some type of interface similar
>> to that.
> 
> That's also a possibility. How about something like:
> 
> if [[ -n "${E_INSTALLED_PKG_METADATA_CMD}" ]] ; then
> ${E_INSTALLED_PKG_METADATA_CMD} >=cat/pkg-1.23 USE foo
> else
> # old vdb stuff
> fi
> 
> with heavy (and checked) restrictions upon legal metadata keys (stuff
> that's in individual files, not environment.bz2)?
> 

That seems fine except it would be handy if it supports something
like the built_with_use -a and -o options since, given your
interface, it would be best to implement those on the package
manager side.

Zac
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHqrYq/ejvha5XGaMRArngAJ0SlTbooCI+5jjxesdF0MnkU0Ym6ACgsstw
5Mp+QGZPTVPGw2LyY7Cmwpk=
=8xmy
-END PGP SIGNATURE-
-- 
gentoo-dev@lists.gentoo.org mailing list