public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mail Delivery System" <MAILER-DAEMON@fastmail.fm>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Undelivered Mail Returned to Sender
Date: Wed, 14 Aug 2002 19:46:34 -0500 (CDT)	[thread overview]
Message-ID: <20020815004634.6A7F09386D@server2.fastmail.fm> (raw)

[-- Attachment #1: Notification --]
[-- Type: text/plain, Size: 457 bytes --]

This is the Postfix program at host fastmail.fm.

I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can
delete your own text from the message returned below.

      The Postfix program

<devx0000@fastmail.fm>: data format error. Command output: devx0000: Mailbox does not exist

[-- Attachment #2: Delivery error report --]
[-- Type: message/delivery-status, Size: 244 bytes --]

[-- Attachment #3: Undelivered Message --]
[-- Type: message/rfc822, Size: 27905 bytes --]

From: gentoo-dev-request@gentoo.org
To: gentoo-dev@gentoo.org
Subject: gentoo-dev digest, Vol 1 #435 - 13 msgs
Date: Fri, 26 Jul 2002 15:52:03 -0500 (CDT)
Message-ID: <20020726205203.25A1BAC62A@chiba.3jane.net>

Send gentoo-dev mailing list submissions to
	gentoo-dev@gentoo.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.gentoo.org/mailman/listinfo/gentoo-dev
or, via email, send a message with subject or body 'help' to
	gentoo-dev-request@gentoo.org

You can reach the person managing the list at
	gentoo-dev-admin@gentoo.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gentoo-dev digest..."


Today's Topics:

   1. Freetype 2.1.2 test results (Spider)
   2. Re: new package notification (Alexander Gretencord)
   3. Re: [gentoo-user] new package notification (Robert Cole)
   4. Re: Automatic menus? (Tom Philbrick)
   5. Re: new package notification (Gregg)
   6. ADV: TIMES ARE TOUGH! WHAT DO YOU DO? (lennd@americandebtsettlement.com)
   7. My Time Problems...Cause Found (Matthew Walker)
   8. Moderator? (Marko Mikulicic)
   9. Re: new package notification (Marko Mikulicic)
  10. Re: new package notification (Gregg)
  11. Re: new package notification (Gregg)
  12. Re: Freetype 2.1.2 test results (Paul de Vrieze)
  13. Re: new package notification (Marko Mikulicic)

--__--__--

Message: 1
Date: Fri, 26 Jul 2002 19:06:12 +0200
From: Spider <spider@gentoo.org>
To: gentoo-dev <gentoo-dev@gentoo.org>
Organization: Chaotic
Subject: [gentoo-dev] Freetype 2.1.2 test results

--=.jgCXk5aa/3MwAL
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

okay, I've done some testing on freetype 2.1.2 

On my x86 system, this build works with pango 1.0.3 and gtk+ 2.0.5

Could other arches please test?

Tests were:
unmask freetype
emerge freetype
emerge -c freetype (no old .so's)
run gedit : worked

emerge pango : worked
emerge gtk+ : worked

thats about it ... more testing is required.


//Spider


--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

--=.jgCXk5aa/3MwAL
Content-Type: application/pgp-signature

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

iD8DBQE9QYGFZS9CZTi033kRAjPdAKCE7PyOtcajWpiwNyY7NyEkzxKPjQCfbnXi
By/rZpINjlRo1Zv9Yg/SZZE=
=x1J3
-----END PGP SIGNATURE-----

--=.jgCXk5aa/3MwAL--


--__--__--

Message: 2
From: Alexander Gretencord <arutha@gmx.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new package notification
Date: Fri, 26 Jul 2002 19:20:26 +0200

On Friday 26 July 2002 18:44, Gregg wrote:
> I want to see a list of new packages that are available after an rsync.
> Not updates to packages that were already there, but new directories in
> the portage tree.

Do a "find /usr/portage/ -type d > before" before the emerge rsync and th=
e=20
same after rsyncing but into file "after". The do a "diff before after".=20
After doing this once you can just move the after file to before everytim=
e so=20
you don't have to do a find before the next rsync but just use the last=20
after-file. You could tell it to not print the files dir so you will only=
 get=20
the new packages directory and not the files dir which holds the digests =
and=20
patches.

just my 2(euro)cent

Alex

--=20
"They that can give up essential liberty to obtain a little temporary saf=
ety=20
deserve neither liberty nor safety."
Benjamin Franklin


--__--__--

Message: 3
From: Robert Cole <robert@support4linux.com>
Reply-To: robert@support4linux.com
Organization: Questnet Linux Training &Services
To: gregg@sc.am, <gentoo-dev@gentoo.org>
Date: Fri, 26 Jul 2002 10:39:36 -0700
Cc: <gentoo-user@gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-user] new package notification

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I think that's a great idea. I do the same as far as keeping my system as=
=20
close to portage as possible. I've had to deviate a little lately but for=
 the=20
most part everything I need is in the tree.

Since you have to do rsync's as root anyway how about just outputting a t=
ext=20
file to /root?

Robert

On Friday 26 July 2002 09:44 am, Gregg wrote:
> I have mentioned this a couple times to usually no response.  I feel th=
at
> it is an important feature , I was hoping to get some sort of response =
to
> this as to  how it should be done, or a response saying "we are already
> working on that". Either way is fine by me :)
>
> I want to see a list of new packages that are available after an rsync.
> Not updates to packages that were already there, but new directories in
> the portage tree.
>
> I keep my gentoo box as close to "portage only" as possible.  It makes
> management easier and makes everything fit together the way it should.
> The Gentoo way.  In doing so, I deny myself some applications taht do n=
ot
> have ebuilds yet.  I would love to see a list after an emerge rsync of
> what NEW packages that were not in my portage before, have been added.
> This will let me see whats new that I might install.
>
> Ideas range from portage keeping a log of what directories it actually
> creates durring rsync and allowing you to output that to a text file.  =
To
> a script you run before and after that builds a list of the directories=
 in
> the tree and compares the 2 lists, showing you the new directories. Im
> sure there are other ways as well.
>
> Any ideas?  Anyone already have this working?
>
>
>
> _______________________________________________
> gentoo-user mailing list
> gentoo-user@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-user
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9QYlYOWbzte5wVEURAgRNAJ0SI1AZd6ldteWr9AvxCaN35tkT0QCeNBQb
bnpvLL8xxpCcj9GMwOPi5PY=3D
=3D2Rp2
-----END PGP SIGNATURE-----


--__--__--

Message: 4
Date: Fri, 26 Jul 2002 13:53:37 -0400
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Automatic menus?
From: Tom Philbrick <tom@wickidpisa.com>

On Fri, Jul 26, 2002 at 02:45:05PM +0200, Corvus Corax wrote:
> Dont want to bother anyone, but the idea of having to rebuild every ebuild existing for menu data seems not very effective.

It would not be very effective, which is why no one, including myself,
has suggested it. The way this would wor is, there is a program called
update-menus that should be called in the ebuild of any program that
installs a menufile. This program reads through /usr/lib/menu/ which
holds all the menufiles that packages have installed, and from these
files it creates a menu for any program that installs a menu-method (a
file describing how to generate a menu for that program). The menufiles
would be added in with the next update to the ebuild (I assume).
Please read the docs for more:
http://www.debian.org/doc/packaging-manuals/menu.html/index.html

--__--__--

Message: 5
Date: Fri, 26 Jul 2002 13:50:06 -0500 (CDT)
Subject: Re: [gentoo-dev] new package notification
From: "Gregg" <gregg@sc.am>
To: <arutha@gmx.de>
Cc: <gentoo-dev@gentoo.org>
Reply-To: gregg@sc.am

So...

Something along these lines is in order:

rm /root/before
rm /root/after
rm /root/new
find /usr/portage -type d | grep -i -v files >/root/before
emerge rsync
find /usr/portage -type d | grep -i -v files >/root/after
diff /root/before /root/after | tee /root/new


That cleans up the old files, buids the before list, emerged, builds the
after (both ignoring the files directory,) and then outputs the diff to
screen and file

Anyone up to making this a neat little script?


> On Friday 26 July 2002 18:44, Gregg wrote:
>> I want to see a list of new packages that are available after an
>> rsync. Not updates to packages that were already there, but new
>> directories in the portage tree.
>
> Do a "find /usr/portage/ -type d > before" before the emerge rsync and
> the  same after rsyncing but into file "after". The do a "diff before
> after".  After doing this once you can just move the after file to
> before everytime so  you don't have to do a find before the next rsync
> but just use the last  after-file. You could tell it to not print the
> files dir so you will only get  the new packages directory and not the
> files dir which holds the digests and  patches.
>
> just my 2(euro)cent
>
> Alex
>
> --
> "They that can give up essential liberty to obtain a little temporary
> safety  deserve neither liberty nor safety."
> Benjamin Franklin
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev




--__--__--

Message: 6
Date: Fri, 26 Jul 2002 11:52:46 -0700
To: gentoo-dev@gentoo.org
From: lennd@americandebtsettlement.com
Organization: Marketing Research International
Subject: [gentoo-dev] ADV: TIMES ARE TOUGH! WHAT DO YOU DO?

<html>
<head>
<title>Untitled Document</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<script language="JavaScript">
<!--
function MM_reloadPage(init) {  //reloads the window if Nav4 resized
  if (init==true) with (navigator) {if ((appName=="Netscape")&&(parseInt(appVersion)==4)) {
    document.MM_pgW=innerWidth; document.MM_pgH=innerHeight; onresize=MM_reloadPage; }}
  else if (innerWidth!=document.MM_pgW || innerHeight!=document.MM_pgH) location.reload();
}
MM_reloadPage(true);
// -->
</script>
<style type="text/css">
<!--
.SMARTER {  font-family: "Times New Roman"; font-size: 60px; font-style: normal; color: #FF0000}
.Justabout {  font-family: Verdana; font-size: 20px; font-style: normal; color: #6699CC}
-->
</style>
</head>

<body bgcolor="#FFFFFF" text="#000000" background="http://www.marketingresearchinternational.com/BOOKsmarterbackground.jpg">
<div id="Layer1" style="position:absolute; width:200px; height:136px; z-index:1; left: 2px; top: -1px"><a href="http://www.marketingresearchinternational.com/booksmarter1.jpg"><img src="http://www.marketingresearchinternational.com/BOOKsmarter1.jpg" width="657" height="135" border="0"></a></div>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<div id="Layer2" style="position:absolute; width:633px; height:64px; z-index:2; left: 26px; top: 185px" class="SMARTER">YOU 
  GET SMARTER.</div>
<p>&nbsp;</p>
<div id="Layer3" style="position:absolute; width:634px; height:60px; z-index:3; left: 23px; top: 304px" class="Justabout"> 
  <div align="center"><font color="#999999" class="Justabout">Just about anyone 
    can make it when times are good.<br>
    Now learn how to succeed in tough times!</font></div>
</div>
<p>&nbsp;</p>
<div id="Layer4" style="position:absolute; width:632px; height:30px; z-index:4; top: 390px; left: 24px"> 
  <div align="center" class="Justabout"><a href="http://www.marketingresearchinternational.com/ebook/ebook.html"><font color="#6699CC">CLICK 
    HERE to Get Smarter!</font></a></div>
</div>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<div id="Layer5" style="position:absolute; width:644px; height:78px; z-index:5; left: 25px; top: 461px">You 
  have signed up with one of our network partners to receive email providing you 
  with special offers. If you do not wish to receive these offers in the future, 
  simply click on the following link:<br>
  <a href="mailto:remove@marketingresearchinternational.com?subject=REMOVE%20ME!%20mir726">Click 
  here to unsubscribe</a></div>
<p><br>
</p>
</body>
</html>


--__--__--

Message: 7
Date: Fri, 26 Jul 2002 12:57:48 -0600 (MDT)
From: "Matthew Walker" <mwalker@kydance.net>
To: <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] My Time Problems...Cause Found

Today, I discovered that the tape backups that run nightly on my computer
are the source of my slowdown. I suspect this is related to DMA somehow, but
I don't know how to turn on DMA on a tape drive. Anyone got any suggestions?

----------------------------------------------------
Matthew Walker                       Kydance Hosting
mwalker@kydance.net       Low Prices, High Standards
                              http://www.kydance.net
Quote:
Schools are prisons for the enlightened mind  --  Me



--__--__--

Message: 8
Date: Fri, 26 Jul 2002 21:52:17 +0200
From: Marko Mikulicic <marko@seul.org>
To: gentoo-dev <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Moderator?

Hello,

I posted a couple of messages and got back:

moderator....
The reason it is being held:

     Message has a suspicious header

What does this mean? It is some
spam blocking filter ?
I suspect it has to do with the attachment.

  It's a bit frustrating to be marked as a spammer :-)

It will be a big promblem when spammers will learn
how to use bugzilla :-)
The only thing I don't like in bugzilla is the latency in
its comunication. For example I have written a little (20 lines)
script and I would like to hear some feedbacks before writing
an ebuild for it and submit it to bugzilla.

Marko Mikulicic


--__--__--

Message: 9
Date: Fri, 26 Jul 2002 21:54:54 +0200
From: Marko Mikulicic <marko@seul.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new package notification

(sorry for posting this message on a new thread but
I had some problems with the headers of the original message)

Gregg wrote:
  > So...
  >
  > Something along these lines is in order:
  >
  > rm /root/before
  > rm /root/after
  > rm /root/new
  > find /usr/portage -type d | grep -i -v files >/root/before
  > emerge rsync
  > find /usr/portage -type d | grep -i -v files >/root/after
  > diff /root/before /root/after | tee /root/new
  >
  >
  > That cleans up the old files, buids the before list, emerged, builds the
  > after (both ignoring the files directory,) and then outputs the diff to
  > screen and file

good. This is a script based on your idea.
It it configurable and sends colorized output with package description
to the screen, while mainaining the log in the file.
    The log file contains only /usr/portage/... files (no diff trash)

The base directory is configurable (default /root) and the files
are called emerge-rsync.before|after|new. However I think it would
be better to store them somewhere in /var (/var/db/pkg/portage/...
/var/log) because I don't like messing in the home directory,
and if we are going to make it a system utility it should be
well integrated.

Marko

script (cannot send attachments):
<snip>
!/bin/sh
BASE=/root
USE_COLORS=yes

# end user configuration section

BEFORE=$BASE/ebuild-rsync.before
AFTER=$BASE/ebuild-rsync.after
NEW=$BASE/ebuild-rsync.new

if [ "$USE_COLORS" == "yes" ]; then
  GREEN="\033[;32m"
  NORMAL="\033[m"
fi

find /usr/portage -type d | grep -i -v files >$BEFORE
emerge rsync
find /usr/portage -type d | grep -i -v files >$AFTER
diff $BEFORE $AFTER | grep /usr/portage | sed "s/> //g" > $NEW

# cleanup
rm $BEFORE $AFTER

# display
echo
echo New ebuilds:
for i in $(cat $NEW); do
  . $(ls $i/*.ebuild --sort=time | head -n 1)

  echo -e $GREEN${i##/usr/portage/}$NORMAL: $DESCRIPTION
done

</snip>





--__--__--

Message: 10
Date: Fri, 26 Jul 2002 15:00:08 -0500 (CDT)
Subject: Re: [gentoo-dev] new package notification
From: "Gregg" <gregg@sc.am>
To: <marko@seul.org>
        
        
        
        
        
        
        
        <200207261920.26542.arutha@gmx.de>
        <2317.12.247.253.40.1027709406.squirrel@sc.am>
        <3D41A376.4060305@seul.org>
Importance: Normal
Cc: <arutha@gmx.de>, <gentoo-dev@gentoo.org>
Reply-To: gregg@sc.am
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: gentoo-dev-admin@gentoo.org
Precedence: bulk
List-Help: <mailto:gentoo-dev-request@gentoo.org?subject=help>
List-Post: <mailto:gentoo-dev@gentoo.org>
List-Subscribe: <http://lists.gentoo.org/mailman/listinfo/gentoo-dev>,
	<mailto:gentoo-dev-request@gentoo.org?subject=subscribe>
List-Id: Gentoo Linux developer list <gentoo-dev.gentoo.org>
List-Unsubscribe: <http://lists.gentoo.org/mailman/listinfo/gentoo-dev>,
	<mailto:gentoo-dev-request@gentoo.org?subject=unsubscribe>
List-Archive: <http://lists.gentoo.org/pipermail/gentoo-dev/>

With proxy's help on the forums we had this one already.  Yours is cleaner
and I like the color output. This one shows whats been removed also. 
Possiby you could merge that ability in as well?

Gregg


#!/bin/sh

# directories in portage to ignore (not used yet)
EXCLUDE="distfiles:files:eclass:licenses:profiles:scripts:metadata:packages"

#check if this is first run
if [ ! -f /var/cache/package.cache ] ; then
    echo "initializing package cache..."
    find /usr/portage/ -type d -mindepth 2 -maxdepth 2 | sort 2>/dev/null
> /va$

else
    # move old cache (to compare to later)
    mv -f /var/cache/package.cache /var/cache/package.old 2>/dev/null

    # create new cache
     echo "Creating cache..."
     find /usr/portage/ -type d -mindepth 2 -maxdepth 2 | sort 2>/dev/null
> /v$
     echo "New:"
     diff /var/cache/package.old /var/cache/package.cache | grep \>
     echo
     echo "Removed:"
     diff /var/cache/package.old /var/cache/package.cache | grep \<
     echo
     echo "Done."
fi




> Gregg wrote:
>> So...
>>
>> Something along these lines is in order:
>>
>> rm /root/before
>> rm /root/after
>> rm /root/new
>> find /usr/portage -type d | grep -i -v files >/root/before
>> emerge rsync
>> find /usr/portage -type d | grep -i -v files >/root/after
>> diff /root/before /root/after | tee /root/new
>>
>>
>> That cleans up the old files, buids the before list, emerged, builds
>> the after (both ignoring the files directory,) and then outputs the
>> diff to screen and file
>
> good. This is a script based on your idea.
> It it configurable and sends colorized output with package description
> to the screen, while mainaining the log in the file.
>   The log file contains only /usr/portage/... files (no diff trash)
>
> The base directory is configurable (default /root) and the files
> are called emerge-rsync.before|after|new. However I think it would be
> better to store them somewhere in /var (/var/db/pkg/portage/...
> /var/log) because I don't like messing in the home directory,
> and if we are going to make it a system utility it should be
> well integrated.
>
> Marko




--__--__--

Message: 11
Date: Fri, 26 Jul 2002 15:03:04 -0500 (CDT)
Subject: Re: [gentoo-dev] new package notification
From: "Gregg" <gregg@sc.am>
To: <marko@seul.org>
        
        
        
        
        
        
        
        <200207261920.26542.arutha@gmx.de>
        <2317.12.247.253.40.1027709406.squirrel@sc.am>
        <3D41A90E.4020408@seul.org>
Importance: Normal
Cc: <gentoo-dev@gentoo.org>
Reply-To: gregg@sc.am
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: gentoo-dev-admin@gentoo.org
Precedence: bulk
List-Help: <mailto:gentoo-dev-request@gentoo.org?subject=help>
List-Post: <mailto:gentoo-dev@gentoo.org>
List-Subscribe: <http://lists.gentoo.org/mailman/listinfo/gentoo-dev>,
	<mailto:gentoo-dev-request@gentoo.org?subject=subscribe>
List-Id: Gentoo Linux developer list <gentoo-dev.gentoo.org>
List-Unsubscribe: <http://lists.gentoo.org/mailman/listinfo/gentoo-dev>,
	<mailto:gentoo-dev-request@gentoo.org?subject=unsubscribe>
List-Archive: <http://lists.gentoo.org/pipermail/gentoo-dev/>

Also, as per my last email with the other script that was being worked on.
 Ive noticed that the find in that one is faster because of the min and
max depth settings.  These 2 seem to be perfect for merging together then
having exactly what we want, with it being quick and easy.

Gregg

> (sorry for posting this message on a new thread but
> I had some problems with the headers of the original message)
>
> Gregg wrote:
>   > So...
>   >
>   > Something along these lines is in order:
>   >
>   > rm /root/before
>   > rm /root/after
>   > rm /root/new
>   > find /usr/portage -type d | grep -i -v files >/root/before
>   > emerge rsync
>   > find /usr/portage -type d | grep -i -v files >/root/after
>   > diff /root/before /root/after | tee /root/new
>   >
>   >
>   > That cleans up the old files, buids the before list, emerged, builds
> the after (both ignoring the files directory,) and then outputs the
> diff to screen and file
>
> good. This is a script based on your idea.
> It it configurable and sends colorized output with package description
> to the screen, while mainaining the log in the file.
>     The log file contains only /usr/portage/... files (no diff trash)
>
> The base directory is configurable (default /root) and the files
> are called emerge-rsync.before|after|new. However I think it would be
> better to store them somewhere in /var (/var/db/pkg/portage/...
> /var/log) because I don't like messing in the home directory,
> and if we are going to make it a system utility it should be
> well integrated.
>
> Marko
>
> script (cannot send attachments):
> <snip>
> !/bin/sh
> BASE=/root
> USE_COLORS=yes
>
> # end user configuration section
>
> BEFORE=$BASE/ebuild-rsync.before
> AFTER=$BASE/ebuild-rsync.after
> NEW=$BASE/ebuild-rsync.new
>
> if [ "$USE_COLORS" == "yes" ]; then
>   GREEN="\033[;32m"
>   NORMAL="\033[m"
> fi
>
> find /usr/portage -type d | grep -i -v files >$BEFORE
> emerge rsync
> find /usr/portage -type d | grep -i -v files >$AFTER
> diff $BEFORE $AFTER | grep /usr/portage | sed "s/> //g" > $NEW
>
> # cleanup
> rm $BEFORE $AFTER
>
> # display
> echo
> echo New ebuilds:
> for i in $(cat $NEW); do
>   . $(ls $i/*.ebuild --sort=time | head -n 1)
>
>   echo -e $GREEN${i##/usr/portage/}$NORMAL: $DESCRIPTION
> done
>
> </snip>
>
>
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev




--__--__--

Message: 12
From: Paul de Vrieze <pauldv@cs.kun.nl>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Freetype 2.1.2 test results
Date: Fri, 26 Jul 2002 22:16:01 +0200

On Friday 26 July 2002 19:06, Spider wrote:
> okay, I've done some testing on freetype 2.1.2
>
> On my x86 system, this build works with pango 1.0.3 and gtk+ 2.0.5
>
> Could other arches please test?
>
> Tests were:
> unmask freetype
> emerge freetype
> emerge -c freetype (no old .so's)
> run gedit : worked
>
> emerge pango : worked
> emerge gtk+ : worked
>
> thats about it ... more testing is required.
>

I also tested this freetype lib, and yes, it worked well. But,... for me,=
 my=20
fonts in mozilla where butt ugly, so I quickly went back to the old versi=
on=20
that (with some setting changes) looks a lot better.

Paul

--=20
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net


--__--__--

Message: 13
Date: Fri, 26 Jul 2002 22:50:41 +0200
From: Marko Mikulicic <marko@seul.org>
To: gregg@sc.am
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new package notification

Gregg wrote:
> Also, as per my last email with the other script that was being worked on.
>  Ive noticed that the find in that one is faster because of the min and
> max depth settings.  These 2 seem to be perfect for merging together then
> having exactly what we want, with it being quick and easy.

Ok. I'm merging the two. I've already implemented the "remove" feture. 
It outputs in red, for consistency, but I don't know if it makes sense.

For the -maxdepth -mindepth:
I'm working to implement the 
EXCLUDE="distfiles:files:eclass:licenses:profiles:scripts:metadata:packages"
feature, but if -maxdepth 2-mindepth 2 is used it is useless because
at this directory level all we have is *.ebuild directories.
  But if the portage system will be extended to have more than two levels
of directories (instead of the "-" trik, like in "x11-libs") we'll
have to switch back.
  Ok. so I drop the EXCLUDE feature.

However the performance gain is ridiculous 0.3 seconds with recursive
vs 0.03 sec with maxdepth 2, given that rsync often takes much much longer.

What about /var/cache for script output ?
Or should I leave /root as default ?

I thought it could be called "emerge-rsync", at least until
we integrate it in emerge itself :-) ok?

I've added command line passing to emerge rysnc (for --clean)
Tell me if you like it.
I will make an ebuild for it, but I cannot provide hosting. Where should 
I put it?

So here is the script:
<snip>
#!/bin/sh
BASE=/var/cache
USE_COLORS=yes

# end user configuration section
. /etc/make.globals
BEFORE=$BASE/ebuild-rsync.before
AFTER=$BASE/ebuild-rsync.after
NEW=$BASE/ebuild-rsync.new
REMOVED=$BASE/ebuild-rsync.removed

if [ "$USE_COLORS" == "yes" ]; then
  RED="\033[;31m"
  GREEN="\033[;32m"
  NORMAL="\033[m"
fi

function portagetree () {
  find $PORTDIR -type d -mindepth 2 -maxdepth 2
}

# do it
portagetree >$BEFORE
emerge $@ rsync
portagetree >$AFTER
diff $BEFORE $AFTER | grep ">" | sed "s/> //g" > $NEW
diff $BEFORE $AFTER | grep "<" | sed "s/< //g" > $REMOVED

# cleanup
rm $BEFORE $AFTER

# display new ebuilds
if ! diff -q $NEW /dev/null >/dev/null; then
  echo
  echo New ebuilds:
  for i in $(cat $NEW); do
   . $(ls $i/*.ebuild --sort=time | head -n 1)
   echo -e $GREEN${i##$PORTDIR/}$NORMAL: $DESCRIPTION
  done
fi

# display removed ebuilds
if ! diff -q $REMOVED /dev/null >/dev/null; then
  echo
  echo Removed ebuilds:
   for i in $(cat $REMOVED); do
      echo -e $RED${i##$PORTDIR/}$NORMAL
   done
fi
</snip>






--__--__--

_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev


End of gentoo-dev Digest


             reply	other threads:[~2002-08-15  0:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15  0:46 Mail Delivery System [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-15  0:46 [gentoo-dev] Undelivered Mail Returned to Sender Mail Delivery System
2002-08-15  0:46 Mail Delivery System
2002-08-15  0:46 Mail Delivery System
2002-08-15  0:46 Mail Delivery System
2002-08-15  0:46 Mail Delivery System
2002-08-15  0:46 Mail Delivery System
2002-08-15  0:46 Mail Delivery System
2002-08-15  0:46 Mail Delivery System

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=20020815004634.6A7F09386D@server2.fastmail.fm \
    --to=mailer-daemon@fastmail.fm \
    --cc=gentoo-dev@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