[gentoo-dev] app-office/openoffice-ximian has got to go
Hi, I'm planning on removing app-office/openoffice-ximian from the tree in a week or so. The package has been superseded by app-office/openoffice-2.0, which has every bonus stuff openoffice-ximian ever had. All archs have now moved over to app-office/openoffice-2.0, so this is the right time to say good bye to openoffice-ximian. Also there already has been a dummy ebuild in place for quite some time, which basically tells the users to move on. let's have a cleaner tree ;) Andreas -- Andreas Proschofsky Gentoo Developer / OpenOffice.org signature.asc Description: This is a digitally signed message part
[gentoo-dev] Last rites for media-libs/xpm
Hello, media-libs/xpm is currently just a dummy ebuild that depends on virtual/x11. All ebuilds in the tree have already been adapted to depend directly on virtual/x11 and/or modular X equivalents. Thus I'm scheduling it for removal within a week or so if nobody complains. Cheers, Marcelo -- Marcelo Góes [EMAIL PROTECTED] [EMAIL PROTECTED] -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Last rites for x11-libs/docklib
Hi, x11-libs/docklib is old, unmaintained and not used. All dockaps that use such library use x11-libs/libdockap already (last was ported today). There's no ebuild that depends on docklib. I've scheduled it for removal on Friday 27/01 if nobody complains (currently p.masked). -- Krzysiek 'Nelchael' Pawlik GPG:0xBC51 signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Last rites for media-libs/xpm
On Sunday 22 January 2006 09:48, Marcelo Góes wrote: > media-libs/xpm is currently just a dummy ebuild that depends on > virtual/x11. All ebuilds in the tree have already been adapted to > depend directly on virtual/x11 and/or modular X equivalents. Thus I'm > scheduling it for removal within a week or so if nobody complains. you cant remove the package until you update the things depending on it xpm is no longer a dummy package, it's x11-libs/libXpm now in modular X terms -mike -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Last rites for media-libs/xpm
On 1/22/06, Mike Frysinger <[EMAIL PROTECTED]> wrote: > On Sunday 22 January 2006 09:48, Marcelo Góes wrote: > > media-libs/xpm is currently just a dummy ebuild that depends on > > virtual/x11. All ebuilds in the tree have already been adapted to > > depend directly on virtual/x11 and/or modular X equivalents. Thus I'm > > scheduling it for removal within a week or so if nobody complains. > > you cant remove the package until you update the things depending on it > > xpm is no longer a dummy package, it's x11-libs/libXpm now in modular X terms > -mike Like I said, this has already been taken care of. There are no more packages that still depend on media-libs/xpm. Instead, they depend either on virtual/x11 or x11-libs/libXpm and whatever else your scripts show... -- Marcelo Góes [EMAIL PROTECTED] [EMAIL PROTECTED] -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Last rites for media-libs/xpm
On Sunday 22 January 2006 12:31, Marcelo Góes wrote: > On 1/22/06, Mike Frysinger <[EMAIL PROTECTED]> wrote: > > On Sunday 22 January 2006 09:48, Marcelo Góes wrote: > > > media-libs/xpm is currently just a dummy ebuild that depends on > > > virtual/x11. All ebuilds in the tree have already been adapted to > > > depend directly on virtual/x11 and/or modular X equivalents. Thus I'm > > > scheduling it for removal within a week or so if nobody complains. > > > > you cant remove the package until you update the things depending on it > > > > xpm is no longer a dummy package, it's x11-libs/libXpm now in modular X > > terms > > Like I said, this has already been taken care of. sorry, i'm a tool > There are no more > packages that still depend on media-libs/xpm. Instead, they depend > either on virtual/x11 or x11-libs/libXpm and whatever else your > scripts show... i have no scripts -mike -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] fix binary debug support, part elevenity billion 1/2
On Saturday 21 January 2006 23:12, Marius Mauch wrote: > Mike Frysinger wrote: > > On Sunday 15 January 2006 01:11, Mike Frysinger wrote: > > > > - we add an emerge flag (say '--debug-build') which adds "debug-build" to > > FEATURES > > IMO this is pointless and redundant. its purpose is to handle cases where user wants to always have a package built in this manner (ferringb mentioned it as a possibility and someone else mentioned they would like it) -mike -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Last rites for media-libs/xpm
On 1/22/06, Mike Frysinger <[EMAIL PROTECTED]> wrote: > i have no scripts > -mike Sorry, I was tripping. The scripts are spyderous's. Marcelo -- Marcelo Góes [EMAIL PROTECTED] [EMAIL PROTECTED] -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] fix binary debug support, part elevenity billion 1/2
On Sun, 22 Jan 2006 14:45:34 -0500 Mike Frysinger <[EMAIL PROTECTED]> wrote: > On Saturday 21 January 2006 23:12, Marius Mauch wrote: > > Mike Frysinger wrote: > > > On Sunday 15 January 2006 01:11, Mike Frysinger wrote: > > > > > > - we add an emerge flag (say '--debug-build') which adds > > > "debug-build" to FEATURES > > > > IMO this is pointless and redundant. > > its purpose is to handle cases where user wants to always have a > package built in this manner (ferringb mentioned it as a possibility > and someone else mentioned they would like it) I meant the option is redundant if it just triggers a feature setting, as it's the same as `FEATURES=debug-build emerge foo` -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better. signature.asc Description: PGP signature
Re: [gentoo-dev] pdf use flags
On Mon, 16 Jan 2006 22:54:49 +0100 Marius Mauch <[EMAIL PROTECTED]> wrote: > So unless there are any objections to this I'll make the change this > weekend. Done. -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better. signature.asc Description: PGP signature
Re: [gentoo-dev] fix binary debug support, part elevenity billion 1/2
On Sunday 22 January 2006 16:30, Marius Mauch wrote: > I meant the option is redundant if it just triggers a feature setting, > as it's the same as `FEATURES=debug-build emerge foo` as noted in earlier proposal: > - no easy way for users/developers to quickly emerge a package and have it > contain useful debugging information, running `FEATURES=nostrip CFLAGS="-g > -O" emerge booga` is petarded -mike -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: RFC - new category dev-tos
Henrik Brix Andersen wrote: > On Sat, Jan 21, 2006 at 08:32:20AM +0100, sanchan wrote: >> And it is easier to add in rsync_exclude if you don't want it... >> But it seems that there is no much consensus for the new category. >> Tomorrow I've planned the final tests on tos-1.1.15 and nesc-1.2.1 that will >> be >> added to dev-embedded if today nobody else vote for dev-tinyos. > > You have my vote for a seperate category... > > ./Brix +1 -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Duplicate licences
Joshua Baergen wrote: The reasons that this system was chosen were correctness and maintainability. Many of these essentially use the good old MIT license with various companies' and/or individuals' copyrights at the top, as you have stated. However, the MIT license does refer to the copyrights within the license script itself, and many of the licenses have been slightly altered to include a company's name directly. I'm no lawyer, but to me this means that the license does indeed include the copyright. (Note that I'm not intricately familiar with other licenses that often have copyrights associated, so I don't know if MIT is unique). If this isn't correct, I'd be very happy to switch all the packages that use various forms of the MIT license over to it instead and you can blissfully ignore the next paragraph. However, I'd rather be on the safe/correct side than save a few MB that have to be downloaded once. Joshua Baergen I'd still like clarification on this. I fully realize that we've been using generalized placeholders for a long time, but that doesn't really matter in the end if it's not legal. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Duplicate licences
On Sun, Jan 22, 2006 at 02:59:39PM -0700, Joshua Baergen wrote: > Joshua Baergen wrote: > >The reasons that this system was chosen were correctness and > >maintainability. Many of these essentially use the good old MIT > >license with various companies' and/or individuals' copyrights at the > >top, as you have stated. However, the MIT license does refer to the > >copyrights within the license script itself, and many of the licenses > >have been slightly altered to include a company's name directly. I'm > >no lawyer, but to me this means that the license does indeed include > >the copyright. (Note that I'm not intricately familiar with other > >licenses that often have copyrights associated, so I don't know if MIT > >is unique). If this isn't correct, I'd be very happy to switch all > >the packages that use various forms of the MIT license over to it > >instead and you can blissfully ignore the next paragraph. However, > >I'd rather be on the safe/correct side than save a few MB that have to > >be downloaded once. > > > > > > > >Joshua Baergen > I'd still like clarification on this. I fully realize that we've been > using generalized placeholders for a long time, but that doesn't really > matter in the end if it's not legal. What leads you to believe the license texts distributed in portage tree are legaly binding with respect to the packages? Each packgage carries (or at least should carry) its license embeded inside. In my understanding, licanse pointers in ebuilds are purely informative and allow you to check the terms of the license (and decide if the license is acceptable) before you actually perform any legaly binding action (like running 'emerge app-foo/bar'). Regards, Peter Cech -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] guide/howto switching to slotted MySQL
Here there is a guide on howto switch to the slotted versions of MySQL.
It's a first draft and to be totally usable some repoman commit are needed.
After the mentioned commits and the needed corrections to the guide
4.1.16 , 5.0.17 and 5.0.18 (all marked unstable) will be removed.
At the same time slotted MySQL will acquire keywording actually owned by
the removed counterparts.
The stabling of MySQL 5.0 will be retarded from 2005-02-15 to 30 days
after the slotted packages keywording.
regards,
Francesco R.
MySQL, upgrade and switch to slotted guide
Francesco Riosa
Here described there is an upgrade path for MySQL databases as painless as
possible.
1.6
2006-01-04
Upgrading from old versions of MySQL
This document cover how to upgrade to the latest version available.
There are currently three version of MySQL supported in portage:
5.0 Follow upstream schedule (stable tree, active bugfixing)
4.1 Follow upstream schedule (only changes to a large userbase)
4.0 Security fix only
There are two additional version presently, but are currently unsupported
meaning that bug reports have very low priority any may lack functionalities.
The current document is not guaranteed to work with them.
3.23 ancient
5.1 active development
The present document will use mysql-4.0.26 as start point
and mysql-5.0.18-r30 as the target version
Replace any of these with your own.
Install the new version
This step require to (re)move some files from the running environment,
so the first thing to do is a backup of the running database server,
(still not the data).
Done that, it's possible to remove the conflicting files with the
slotted MySQL, and install the new version side by side with
the current one.
# quickpkg dev-db/mysql
# rm -rf /usr/include/mysql /usr/bin/mysql_config
# for tmpfile in /usr/lib/*mysql* ; do
mv "${tmpfile}" "${tmpfile}.TMP"
ln -s "${tmpfile}.TMP" "${tmpfile}"
done
# emerge -av =dev-db/mysql-5.0.18-r30
Be sure to update the /etc/init.d/mysql startup script with
etc-update or dispatch-conf.
Copy the data to the newly installed server
Lets go to to dump the data, this will be imported in the new version of
mysql.
We are going to use mysqldump from the slotted MySQL.
Notice the "-500" suffix to the mysqldump program name, it's from
the 5.0.x version.
# mysqldump-500 \
--defaults-file=/etc/mysql/my.cnf
-uroot \
--password='your_password' \
-hlocalhost \
--all-databases \
--opt \
--allow-keywords \
--flush-logs \
--hex-blob \
--master-data \
--max_allowed_packet=16M \
--quote-names \
--result-file=BACKUP_MYSQL_4.0.SQL
Now a file named BACKUP_MYSQL_4.0.SQL exist, which can be
used to recreate your data. The data is described in the MySQL dialect of SQL,
the Structured Query Language.
start the server without networking and user management
and run the SQL script:
# mv /etc/conf.d/mysql /etc/conf.d/mysql.orig
# echo '
NOCHECK=1
DEBUG=3
mysql_slot_500=(
"skip-networking"
"skip-grant-tables"
)
' > /etc/conf.d/mysql
# /etc/init.d/mysql-500 start
# mysql-500 --defaults-file=/etc/mysql-500/my.cnf < BACKUP_MYSQL_4.0.SQL
# mv /etc/conf.d/mysql.orig /etc/conf.d/mysql
# /etc/init.d/mysql-500 stop
To convert the data to UTF-8 during this step you MUST remove "--hex-blob"
from the mysqldump option, then filter the data through a converter like
"iconv".
In most case this is done simply "piping" it like this:
"iconv -f ISO_8859-1 -t UTF8 BACKUP_MYSQL_4.0.SQL
| mysql-500 --defaults-file=/etc/mysql-500/my.cnf"
Also manual tweaking of the SQL file could be needed, depending on the
structure and the data contained in it.
If there are applications still writing to the previous
database, it's possible to setup a "Replication" relationship between the
two databases, however this will not be covered here.
Switch to the new server
If you need to be sure that applications are working with the newly
installed server, please test them against it, quite every application
has configuration settings to chose which port or socket to use to connect
to the database server.
Simply start the server on an alternate port (for example 3307) and tell your
application or a test copy of it to connect with those parameters.
Pay attention that most of them will try to use the parameters found in the
"[client]" section of /etc/mysql/my.cnf config file.
When you're satisfied with the results, remove every testing setting,
stop the old server and start the new one.
Also make it the server that will start at next reboot.
# rc-update del mysql default
# rc-update add mysql-500 default
# /etc/init.d/mysql stop
# /etc/init.d/mysql-500 start
unmerge the old version, and make the new one the default.
The unmerge command will be unable to remove some files, the ones moved in
Backup old package and prepare installation
This is an intended behavior, and avoid breaking application linked to
Re: [gentoo-dev] fix binary debug support, part elevenity billion 1/2
Marius Mauch wrote: > On Sun, 22 Jan 2006 14:45:34 -0500 > Mike Frysinger <[EMAIL PROTECTED]> wrote: > >> On Saturday 21 January 2006 23:12, Marius Mauch wrote: >>> Mike Frysinger wrote: On Sunday 15 January 2006 01:11, Mike Frysinger wrote: - we add an emerge flag (say '--debug-build') which adds "debug-build" to FEATURES >>> IMO this is pointless and redundant. >> its purpose is to handle cases where user wants to always have a >> package built in this manner (ferringb mentioned it as a possibility >> and someone else mentioned they would like it) > > I meant the option is redundant if it just triggers a feature setting, > as it's the same as `FEATURES=debug-build emerge foo` OK, where's my package.features and packages.cflags files then? I can do what I want through Mike's proposal, which is to build a specific collection of packages with debugging. I also don't need to duplicate the same list of packages in one file with FEATURES=nostrip and in another with debugging CFLAGS. Thanks, Donnie signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] guide/howto switching to slotted MySQL
On Monday 23 January 2006 10:06, Francesco Riosa wrote: > Here there is a guide on howto switch to the slotted versions of MySQL. > It's a first draft and to be totally usable some repoman commit are needed. You're probably better of putting this in bugzilla and assigning to the docs team. Please cc me as when you do make one. Chris White pgp2wd19Kclz8.pgp Description: PGP signature
Re: [gentoo-dev] Duplicate licences
Peter Cech wrote: What leads you to believe the license texts distributed in portage tree are legaly binding with respect to the packages? Each packgage carries (or at least should carry) its license embeded inside. In my understanding, licanse pointers in ebuilds are purely informative and allow you to check the terms of the license (and decide if the license is acceptable) before you actually perform any legaly binding action (like running 'emerge app-foo/bar'). Regards, Peter Cech Well, from the documentation, all I have to go on is: "This variable specifies what license the program is covered under, i.e. GPL-2, BSD, etc..."[1] I interpret that as the actual license of the software. It's not made clear that LICENSE points to a generalized representation (although I find that solution much more rational) or that it points to the actual software license. It appears that the people who feel most comfortable with the current solution are those who have been around a good deal of time, which would indicate to me that the reason that things are done now was made a while ago but never documented. [1] http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 -- gentoo-dev@gentoo.org mailing list
