Re: [gentoo-dev] New project: Gentoo Artwork
This year I'm thinking of just doing lightscribe media, much easier then having to deal with labels, the don't come off and they don't wear out. We didn't have any problems with the printable media by Verbatim [1]. Well - of course you shouldn't shower them [2]. ;) Anyways. I just joined the artwork project yesterday to help out with label artwork. So if you need something - poke me. [1] http://www.verbatim-europe.com/index/articles_view.php?article_id=1899lang_id=1 [2] http://planet.gentoo.org/developers/pylon/2006/09/23/i_showered_my_gentoo_cds -- Christian Hartmann http://www.gentoo.org/~ian/ PGP Key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x2154E5EE692A4865 Key fingerprint = 4544 EC0C BAE4 216F 5981 7F95 2154 E5EE 692A 4865 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] gentoo: static/dynamic linking libraries
Am Montag 30 April 2007 05:35 schrieb Marius Mauch: [snip] builds being irrelevant in many cases is wrong, just that the claim of only 2 packages needing it is bogus. Surely this was meant in the context of the previous thread: 2 out of 845 packages on my system would be right. That's about 0,237%. Either way this is a small percentage to argue that 100% should be built with static libs. (And there is still the question whether those two would really _need_ those static libs or it's just due to the deficiency of the EXTRA_ECONF-method.) When I have time I will take a look on how some other distributions handle this. pgpRKPgP4NiOB.pgp Description: PGP signature
[gentoo-dev] Re: gentoo: static/dynamic linking libraries
Roman Zimmermann [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Mon, 30 Apr 2007 09:28:16 +0200: Am Montag 30 April 2007 05:35 schrieb Marius Mauch: [snip] builds being irrelevant in many cases is wrong, just that the claim of only 2 packages needing it is bogus. Surely this was meant in the context of the previous thread: 2 out of 845 packages on my system would be right. That's about 0,237%. Either way this is a small percentage to argue that 100% should be built with static libs. (And there is still the question whether those two would really _need_ those static libs or it's just due to the deficiency of the EXTRA_ECONF-method.) When I have time I will take a look on how some other distributions handle this. What most other distributions (which are binary) do doesn't apply, because they aren't designed for the end-user to be constantly compiling stuff as is assumed on Gentoo. Most other distributions can (and probably do) split most libraries into main-package and -dev package, the -dev version containing headers and likely static versions of the libraries, while the dynamically linked binaries, config, etc, is in the main package. That makes no sense for an end-user compiled distribution, where if a library is installed, it's assumed it will be used, and to use it headers and the like must be installed as well. Statically linked library binaries won't always be needed, true, but IMO the same idea should apply -- they should be installed by default as it'll be impossible to link something statically against them if they aren't, and where end-user compiling must be assumed, it's entirely reasonable to assume those same end-users may wish some of those compilations to be statically built. Sure, if it's not too much of a hassle, give those users a USE flag (since we're talking per-package enabling), that can of course be set globally in make.conf if desired, and that defaults to installing static as well as dynamic for most profiles. Embedded may wish to disable it by default, and users may do so if desired, but in the general case, the static libs should be there by default just in case. However, if it's too much hassle, having both installed is the sane default, and there's certainly INSTALL_MASK for those such as embedded that might be tight-up on space or the required additional compiling resources. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list
[gentoo-dev] Last rites for eclipse-pydev-bin
+# Petteri Räty [EMAIL PROTECTED] (30 Apr 2007) +# Please use the Eclipse update manager to install this. +# This ebuild is for Eclipse 3.0 which is going away. If you want +# this to be installable via emerge, please submit a from source ebuild +# that works with 3.2. (Might not be as easy as it sounds). In Java +# junkyard after 30 days. +dev-util/eclipse-pydev-bin + signature.asc Description: OpenPGP digital signature
[gentoo-dev] Last rites for Eclipse plugins for old versions
These all had wrong DEPEND lines and actually require a package.masked version of eclipse-sdk. Nowadays the plugin manager should be used to install binary plugins any way. # Petteri Räty [EMAIL PROTECTED] (30 Apr 2007) -# Please use the Eclipse update manager to install this. -# This ebuild is for Eclipse 3.0 which is going away. If you want -# this to be installable via emerge, please submit a from source ebuild -# that works with 3.2. (Might not be as easy as it sounds). In Java -# junkyard after 30 days. +# Please use the Eclipse update manager to install these. +# The ebuilds are for Eclipse 3.2 and those versions are going to be +# removed. If you want these to be installable via emerge, please submit from +# source ebuilds that work with 3.2. (Might not be as easy as it sounds). In +# Java junkyard after 30 days. If there is a compelling reason to keep these, +# please mail gentoo-java mailing list or [EMAIL PROTECTED] +dev-util/eclipse-cbg-editor +dev-util/eclipse-cdt-bin +dev-util/eclipse-emf-bin +dev-util/eclipse-gef-bin dev-util/eclipse-pydev-bin +dev-util/eclipse-subclipse-bin +dev-util/eclipse-ve-bin signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Looking for help with 2.6 kernel maintenance
Daniel, I would love to be more involved in kernel details. I've been in gentoo-mips for a long time and considering that I have no more mips hardware to speak of, my ability to do developer related things has diminished. However, I still wish to see Gentoo flurish and more importantly I want to be more involved in kernel level activity. I meed your basic requirements, you can find me on #gentoo-mips if you wish to talk further. Thank you for your time and have a great day -- Bret (psi29a) Curtis -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] New project: Gentoo Artwork
On Sat, 2007-04-28 at 22:04 -0400, William L. Thomson Jr. wrote: On Fri, 2007-04-27 at 11:28 +0200, Bjarke Istrup Pedersen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It would be nice if there where some CD/DVD labels created, that people could print and put on their LiveCDs/InstallCDs :-) Yes that would be quit nice. At LWE in 06 we were handing out cds we were burning with hand written labels. So for any events were we give out livecds and etc. Would make a big difference at least in first impressions for many, IMHO. Release Engineering has had labels for some time. It's just that nobody asks for them. Look on the store for examples of what they look like. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] gentoo: static/dynamic linking libraries
On Mon, 30 Apr 2007 05:07:00 +0200 Roman Zimmermann [EMAIL PROTECTED] wrote: Am Montag 30 April 2007 00:11 schrieb Ciaran McCreesh: On Sun, 29 Apr 2007 14:56:57 -0700 Donnie Berkholz [EMAIL PROTECTED] wrote: Anyone who wants to build a static binary wants the static libs. Given the difficulty in universally enabling or disabling their builds because of build-system differences, building them and tossing them in the trash with INSTALL_MASK, as Marius suggested, seems like the best way to go. The best way to go or the only viable short term solution? Best way to go, IMO. That's the point! Universally disabling static builds can't be a longterm solution. The only sane way to do this is on a per ebuild basis. The thing about static libraries, is that the ebuild that creates them doesn't know whether anything else will want to use them. It may be that in practice, most libraries are never used in their static form - but the point is that the ebuild doesn't know enough information to make the decision. However, with INSTALL_MASK, the user makes the decision never to have static binaries, and thus gets a system free of static libraries. -- Kevin F. Quinn signature.asc Description: PGP signature
Re: [gentoo-dev] Our profiles/updates handling is not smart enough
On Friday 27 April 2007, Marius Mauch wrote: I used to remove old updates files from time to time in the past, guess it's time to do it again. that doesnt sound like a good idea to me at all ... -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] Re: That time again...
On Thu, Apr 26, 2007 at 08:29:43PM +0200, Christian Faulhammer wrote: You are declared official Project Status Report Gathering Manager. I have to concede, I saw this last thursday and sat on it all weekend, mulling it over. I realize you (most likely) meant it as a joke, but for what its worth, I think I'd suck at it if I had to do it consistently. That said...expect more until someone does take up the role ;) Now figuring out how to get this stuff rolled into the gwn (i smell an email to gwn-feedback in my future, I know) so that it could get better coverage (since the mudrakers only look to -dev for the flame wars, not the fun stuff). ~mcummings -- -o()o-- Michael Cummings |#gentoo-dev, #gentoo-perl Gentoo Perl Dev|on irc.freenode.net Gentoo/SPARC Gentoo/AMD64 GPG: 0543 6FA3 5F82 3A76 3BF7 8323 AB5C ED4E 9E7F 4E2E -o()o-- Hi, I'm a .signature virus! Please copy me in your ~/.signature. pgpQubYJ8erDO.pgp Description: PGP signature
[gentoo-dev] Last rites for dev-java/dbconnectionbroker-bin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +# Vlastimil Babka [EMAIL PROTECTED] (30 Apr 2007) +# Stale upstream (since 2002), -bin library that nothing in tree uses +# so it's not needed. Will be removed into java junkyard around 30 May. +dev-java/dbconnectionbroker-bin - -- Vlastimil Babka (Caster) Gentoo/Java -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGNkJrtbrAj05h3oQRAgdcAJ9zfIc+QCYDuBDcF+8WYq868Z4cwQCfd7c4 3aZHjaXVscwsIRV3Nz9vyHk= =iAnA -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
[gentoo-dev] Last rites for dev-java/dbconnectionbroker-bin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 # Vlastimil Babka [EMAIL PROTECTED] (30 Apr 2007) +# Fetch-restricted binary library that nothing in tree uses, upstream +# unsupported (EOL). Will be removed into java junkyard around 30 May. +dev-java/infobus-bin - -- Vlastimil Babka (Caster) Gentoo/Java -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGNmF+tbrAj05h3oQRAn//AJ9fme1lYkxhM5NlR+ICWvHBw9dmMACgnQgu UQ0XLkoj3kJKGpCLIkAYQo4= =0OXK -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] New project: Gentoo Artwork
On Fri, 2007-04-27 at 01:18 +0200, Dawid Węgliński wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there As a fresh developer i would like to introduce you all new subproject I have just started. It is Gentoo Artwork Project. Its official webpage is under [1]. Project consists of two members so far, so this is why we enlist everyone who would like to help us in creating artwork gentoo-related stuff. Do not forget to visit us in #gentoo-artwork. :) @ GWN - could you guys write about us in the next version of gwn please? [1]. http://www.gentoo.org/proj/en/desktop/artwork/index.xml Please get with me some time over the next week as I'd like to discuss a few things. We've been doing some artwork wrt our releases and would *love* to have your project take over that work, which means I might have a recruit for you. ;] -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] New project: Gentoo Artwork
On Fri, 2007-04-27 at 14:44 +0200, Timothy Redaelli wrote: IIRC the problem is only for the Windows icons http://web.archive.org/web/20060223065658/www.gentoo.org/dyn/icons/WIN.xml ...and IE, and Mozilla, and Google, and... Most of those icons were made and put up with absolutely no regard to trademarks, copyrights, or licensing. Rather than try to determine which were legal we decided to pull them. The Artwork project will be fully able to make a replacement set, and we'll expect them to adhere to any legal issues that may arise. If there's question about a particular icon being used, it can be deferred to the trustees to determine. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] gentoo: static/dynamic linking libraries
On Sun, 2007-04-29 at 23:50 +0200, Rémi Cardona wrote: Open Question part: Since I don't have any thing other than Gentoo : does anyone know how other distros handle static libs in their -dev packages? Fedora's policy [1] is to only include static libraries when absolutely necessary, such as with libpci or other libraries that ship *only* static incarnations (though in these cases the packager is heavily encouraged to pester the upstream developer(s) about building a shared library as well); or for specific exceptions where full and satisfactory reason is given for the inclusion of static libraries (such as, perhaps, low-level rescue utilities like grub and others, though they generally then need to explicitly be in a foo-static subpackage when built). All such cases need to be approved by the Fedora Engineering Steering Committee (FESCo). Does anyone care about static libs except for maybe really really low level stuff? They are useful for rescue operations and whatnot, when a LiveCD or similar is not handy; or perhaps when the computer cannot boot from an alternative medium. That's the only major benefit I see of them. My Opinion part: I'd definitely would like to see them leave my system for good as I have no use for 99% of them whatsoever. ++ Open Question part: Could some FEATURE disable static libs building by default in desktop profiles, with some (like the 5 packages Roman pointed out) using something like a RESTRICT? Back when I used Gentoo (mid-2003 through Nov. 2005), I remember there being a -static flag that could be set. I don't remember if that was in FEATURES or USE though; and not all ebuilds honored it. :| Is there similar functionality in modern Portage? [1] http://fedoraproject.org/wiki/Packaging/Guidelines#StaticLibraries -- Peter Gordon (codergeek42) / FSF EFF Member Gentoo Forums Global Moderator GnuPG Public Key ID: 0xFFC19479 / Fingerprint: DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479 My Blog: http://thecodergeek.com/blog/ signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] New project: Gentoo Artwork
Chris Gianelloni wrote: Please get with me some time over the next week as I'd like to discuss a few things. We've been doing some artwork wrt our releases and would *love* to have your project take over that work, which means I might have a recruit for you. ;] I was hoping the artwork team could collaborate with you on labels, i.e. artwork team comes up with the theme designs and releng implements them in CD label form. But whoever wants to do the work and has the time to do it ... Thanks, Donnie signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] gentoo: static/dynamic linking libraries
Peter Gordon wrote: Back when I used Gentoo (mid-2003 through Nov. 2005), I remember there being a -static flag that could be set. I don't remember if that was in FEATURES or USE though; and not all ebuilds honored it. :| Is there similar functionality in modern Portage? As was explained elsewhere in this thread by Marius, that's not what the static flag controls. For your convenience: Marius Mauch wrote: What decision? That USE=static shouldn't be used for (not) installing static libraries is simply because the flag is used to control how (parts of) a package should be linked and global flags shouldn't be used for completely different purposes. That's been the case since the beginning, so I doubt you'll find any dicussion about it. Thanks, Donnie signature.asc Description: OpenPGP digital signature
