[suggest] Recent changes to RPMforge

[Dag Wieers]

Hi,

RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments.

Here is a summary of changes that recently happened to RPMforge.

= RPMforge provides Red Hat Enterprise Linux 6 packages

With the advent of Red Hat Enterprise Linux 6, RPMforge provides many
packages built specifically for RHEL6.


= RPMforge now consists of more than one repository:

+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)

For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

This change can result today in unresolved dependencies that did not
happen in the past (mostly regarding perl packages). In case you have
such a problem, please report those to one of our mailinglists.

Users that in the past used RPMforge without special measures to
protect base packages (yum protectbase or priorities plugins) are
advised to enable rpmforge-extras once, to update to rfx-tagged
packages. Afterwards include only those packages with a seperate
includepkgs= statement in the .repo file.


= DKMS packages for RHEL5 have been removed

RPMforge is working closely together with ELRepo, another third-party
repository specialized in kernel modules (drivers and kernel-related
functionality). Since their kmod RPM packages are using a modern
replacement for DKMS that in many situations are superior to DKMS, we
see no need in providing DKMS packages (especially since they have not
been maintained for some time).

Users that have been using DKMS packages from RPMforge on RHEL5 are
invited to migrate to ELRepo. For more information regarding ELRepo,
please visit their website at:

http://elrepo.org/

In case of questions, please resort to the RPMforge mailinglist at:

http://lists.rpmforge.net/

Kind regards,

[Ingvar Hagelund]

* Dag Wieers

Post by Dag Wieers
RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments. (...)
+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)
For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

First: This is GREAT news. Thank you so much.

Second: This may be a FAQ, but anyway; will there be much overlap
between rpmforge and epel, or will you try to avoid parallell work by
skip packages that exists in epel? (In short: Is it a goal to make
rpmforge and epel more compatible?)

(I may ask the same question about the centos repos, but we can let that
be for now.)

Ingvar

[Dag Wieers]

Post by Ingvar Hagelund
* Dag Wieers

Post by Dag Wieers
RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments. (...)
+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)
For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

First: This is GREAT news. Thank you so much.
Second: This may be a FAQ, but anyway; will there be much overlap
between rpmforge and epel, or will you try to avoid parallell work by
skip packages that exists in epel? (In short: Is it a goal to make
rpmforge and epel more compatible?)

The reason why EPEL is not compatible with RPMforge dates back to the days
when Fedora was started. We already were packaging for Red Hat and RHEL,
and were interested in Fedora too. Fedora Extras did not exist in those
days.

It was clear that Fedora was not interested in RHEL packages at that time
and since that was our main focus anyway, collaboration was no option (you
can find those discussions on the Fedora mailinglist archives). It was
rather painful.

Anyway, a few years ago some people in the Fedora community became
interested in RHEL packages, and so they started from their own collection
of packages, which by then were not compatible with what we already had.
Hence the current situation.

I think both we as well as EPEL are interested in becoming compatible, but
unfortunately that's something that is very hard to achieve, not only
because it requires a lot of communication (which is seen as an impediment
to someone's work) but also that nobody wants to carry the effort.

I have some ideas on how we could improve the situation, and which could
eventually lead to compatibility with EPEL. And in fact made some
modifications to my buildsystem to test whether this would be possible,
but because there are some more important issues to address I don't think
it is a good time to introduce that now.

[Dag Wieers]

Post by Ingvar Hagelund
* Dag Wieers

Post by Dag Wieers
RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments. (...)
+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)
For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

First: This is GREAT news. Thank you so much.
Second: This may be a FAQ, but anyway; will there be much overlap
between rpmforge and epel, or will you try to avoid parallell work by
skip packages that exists in epel? (In short: Is it a goal to make
rpmforge and epel more compatible?)

The reason why EPEL is not compatible with RPMforge dates back to the days
when Fedora was started. We already were packaging for Red Hat and RHEL,
and were interested in Fedora too. Fedora Extras did not exist in those
days.

It was clear that Fedora was not interested in RHEL packages at that time
and since that was our main focus anyway, collaboration was no option (you
can find those discussions on the Fedora mailinglist archives). It was
rather painful.

Anyway, a few years ago some people in the Fedora community became
interested in RHEL packages, and so they started from their own collection
of packages, which by then were not compatible with what we already had.
Hence the current situation.

I think both we as well as EPEL are interested in becoming compatible, but
unfortunately that's something that is very hard to achieve, not only
because it requires a lot of communication (which is seen as an impediment
to someone's work) but also that nobody wants to carry the effort.

I have some ideas on how we could improve the situation, and which could
eventually lead to compatibility with EPEL. And in fact made some
modifications to my buildsystem to test whether this would be possible,
but because there are some more important issues to address I don't think
it is a good time to introduce that now.

[Dag Wieers]

Post by Ingvar Hagelund
* Dag Wieers

Post by Dag Wieers
RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments. (...)
+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)
For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

First: This is GREAT news. Thank you so much.
Second: This may be a FAQ, but anyway; will there be much overlap
between rpmforge and epel, or will you try to avoid parallell work by
skip packages that exists in epel? (In short: Is it a goal to make
rpmforge and epel more compatible?)

The reason why EPEL is not compatible with RPMforge dates back to the days
when Fedora was started. We already were packaging for Red Hat and RHEL,
and were interested in Fedora too. Fedora Extras did not exist in those
days.

It was clear that Fedora was not interested in RHEL packages at that time
and since that was our main focus anyway, collaboration was no option (you
can find those discussions on the Fedora mailinglist archives). It was
rather painful.

Anyway, a few years ago some people in the Fedora community became
interested in RHEL packages, and so they started from their own collection
of packages, which by then were not compatible with what we already had.
Hence the current situation.

I think both we as well as EPEL are interested in becoming compatible, but
unfortunately that's something that is very hard to achieve, not only
because it requires a lot of communication (which is seen as an impediment
to someone's work) but also that nobody wants to carry the effort.

I have some ideas on how we could improve the situation, and which could
eventually lead to compatibility with EPEL. And in fact made some
modifications to my buildsystem to test whether this would be possible,
but because there are some more important issues to address I don't think
it is a good time to introduce that now.

[Dag Wieers]

Post by Ingvar Hagelund
* Dag Wieers

Post by Dag Wieers
RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments. (...)
+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)
For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

First: This is GREAT news. Thank you so much.
Second: This may be a FAQ, but anyway; will there be much overlap
between rpmforge and epel, or will you try to avoid parallell work by
skip packages that exists in epel? (In short: Is it a goal to make
rpmforge and epel more compatible?)

The reason why EPEL is not compatible with RPMforge dates back to the days
when Fedora was started. We already were packaging for Red Hat and RHEL,
and were interested in Fedora too. Fedora Extras did not exist in those
days.

It was clear that Fedora was not interested in RHEL packages at that time
and since that was our main focus anyway, collaboration was no option (you
can find those discussions on the Fedora mailinglist archives). It was
rather painful.

Anyway, a few years ago some people in the Fedora community became
interested in RHEL packages, and so they started from their own collection
of packages, which by then were not compatible with what we already had.
Hence the current situation.

I think both we as well as EPEL are interested in becoming compatible, but
unfortunately that's something that is very hard to achieve, not only
because it requires a lot of communication (which is seen as an impediment
to someone's work) but also that nobody wants to carry the effort.

I have some ideas on how we could improve the situation, and which could
eventually lead to compatibility with EPEL. And in fact made some
modifications to my buildsystem to test whether this would be possible,
but because there are some more important issues to address I don't think
it is a good time to introduce that now.

[Dag Wieers]

Post by Ingvar Hagelund
* Dag Wieers

Post by Dag Wieers
RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments. (...)
+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)
For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

First: This is GREAT news. Thank you so much.
Second: This may be a FAQ, but anyway; will there be much overlap
between rpmforge and epel, or will you try to avoid parallell work by
skip packages that exists in epel? (In short: Is it a goal to make
rpmforge and epel more compatible?)

The reason why EPEL is not compatible with RPMforge dates back to the days
when Fedora was started. We already were packaging for Red Hat and RHEL,
and were interested in Fedora too. Fedora Extras did not exist in those
days.

It was clear that Fedora was not interested in RHEL packages at that time
and since that was our main focus anyway, collaboration was no option (you
can find those discussions on the Fedora mailinglist archives). It was
rather painful.

Anyway, a few years ago some people in the Fedora community became
interested in RHEL packages, and so they started from their own collection
of packages, which by then were not compatible with what we already had.
Hence the current situation.

I think both we as well as EPEL are interested in becoming compatible, but
unfortunately that's something that is very hard to achieve, not only
because it requires a lot of communication (which is seen as an impediment
to someone's work) but also that nobody wants to carry the effort.

I have some ideas on how we could improve the situation, and which could
eventually lead to compatibility with EPEL. And in fact made some
modifications to my buildsystem to test whether this would be possible,
but because there are some more important issues to address I don't think
it is a good time to introduce that now.

[Dag Wieers]

Hi,

RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments.

Here is a summary of changes that recently happened to RPMforge.

= RPMforge provides Red Hat Enterprise Linux 6 packages

With the advent of Red Hat Enterprise Linux 6, RPMforge provides many
packages built specifically for RHEL6.


= RPMforge now consists of more than one repository:

+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)

For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

This change can result today in unresolved dependencies that did not
happen in the past (mostly regarding perl packages). In case you have
such a problem, please report those to one of our mailinglists.

Users that in the past used RPMforge without special measures to
protect base packages (yum protectbase or priorities plugins) are
advised to enable rpmforge-extras once, to update to rfx-tagged
packages. Afterwards include only those packages with a seperate
includepkgs= statement in the .repo file.


= DKMS packages for RHEL5 have been removed

RPMforge is working closely together with ELRepo, another third-party
repository specialized in kernel modules (drivers and kernel-related
functionality). Since their kmod RPM packages are using a modern
replacement for DKMS that in many situations are superior to DKMS, we
see no need in providing DKMS packages (especially since they have not
been maintained for some time).

Users that have been using DKMS packages from RPMforge on RHEL5 are
invited to migrate to ELRepo. For more information regarding ELRepo,
please visit their website at:

http://elrepo.org/

In case of questions, please resort to the RPMforge mailinglist at:

http://lists.rpmforge.net/

Kind regards,

[Dag Wieers]

Hi,

RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments.

Here is a summary of changes that recently happened to RPMforge.

= RPMforge provides Red Hat Enterprise Linux 6 packages

With the advent of Red Hat Enterprise Linux 6, RPMforge provides many
packages built specifically for RHEL6.


= RPMforge now consists of more than one repository:

+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)

For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

This change can result today in unresolved dependencies that did not
happen in the past (mostly regarding perl packages). In case you have
such a problem, please report those to one of our mailinglists.

Users that in the past used RPMforge without special measures to
protect base packages (yum protectbase or priorities plugins) are
advised to enable rpmforge-extras once, to update to rfx-tagged
packages. Afterwards include only those packages with a seperate
includepkgs= statement in the .repo file.


= DKMS packages for RHEL5 have been removed

RPMforge is working closely together with ELRepo, another third-party
repository specialized in kernel modules (drivers and kernel-related
functionality). Since their kmod RPM packages are using a modern
replacement for DKMS that in many situations are superior to DKMS, we
see no need in providing DKMS packages (especially since they have not
been maintained for some time).

Users that have been using DKMS packages from RPMforge on RHEL5 are
invited to migrate to ELRepo. For more information regarding ELRepo,
please visit their website at:

http://elrepo.org/

In case of questions, please resort to the RPMforge mailinglist at:

http://lists.rpmforge.net/

Kind regards,

[Ingvar Hagelund]

* Dag Wieers

Post by Dag Wieers
RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments. (...)
+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)
For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

First: This is GREAT news. Thank you so much.

Second: This may be a FAQ, but anyway; will there be much overlap
between rpmforge and epel, or will you try to avoid parallell work by
skip packages that exists in epel? (In short: Is it a goal to make
rpmforge and epel more compatible?)

(I may ask the same question about the centos repos, but we can let that
be for now.)

Ingvar

[Dag Wieers]

Hi,

RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments.

Here is a summary of changes that recently happened to RPMforge.

= RPMforge provides Red Hat Enterprise Linux 6 packages

With the advent of Red Hat Enterprise Linux 6, RPMforge provides many
packages built specifically for RHEL6.


= RPMforge now consists of more than one repository:

+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)

For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

This change can result today in unresolved dependencies that did not
happen in the past (mostly regarding perl packages). In case you have
such a problem, please report those to one of our mailinglists.

Users that in the past used RPMforge without special measures to
protect base packages (yum protectbase or priorities plugins) are
advised to enable rpmforge-extras once, to update to rfx-tagged
packages. Afterwards include only those packages with a seperate
includepkgs= statement in the .repo file.


= DKMS packages for RHEL5 have been removed

RPMforge is working closely together with ELRepo, another third-party
repository specialized in kernel modules (drivers and kernel-related
functionality). Since their kmod RPM packages are using a modern
replacement for DKMS that in many situations are superior to DKMS, we
see no need in providing DKMS packages (especially since they have not
been maintained for some time).

Users that have been using DKMS packages from RPMforge on RHEL5 are
invited to migrate to ELRepo. For more information regarding ELRepo,
please visit their website at:

http://elrepo.org/

In case of questions, please resort to the RPMforge mailinglist at:

http://lists.rpmforge.net/

Kind regards,

[Dag Wieers]

Hi,

RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments.

Here is a summary of changes that recently happened to RPMforge.

= RPMforge provides Red Hat Enterprise Linux 6 packages

With the advent of Red Hat Enterprise Linux 6, RPMforge provides many
packages built specifically for RHEL6.


= RPMforge now consists of more than one repository:

+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)

For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

This change can result today in unresolved dependencies that did not
happen in the past (mostly regarding perl packages). In case you have
such a problem, please report those to one of our mailinglists.

Users that in the past used RPMforge without special measures to
protect base packages (yum protectbase or priorities plugins) are
advised to enable rpmforge-extras once, to update to rfx-tagged
packages. Afterwards include only those packages with a seperate
includepkgs= statement in the .repo file.


= DKMS packages for RHEL5 have been removed

RPMforge is working closely together with ELRepo, another third-party
repository specialized in kernel modules (drivers and kernel-related
functionality). Since their kmod RPM packages are using a modern
replacement for DKMS that in many situations are superior to DKMS, we
see no need in providing DKMS packages (especially since they have not
been maintained for some time).

Users that have been using DKMS packages from RPMforge on RHEL5 are
invited to migrate to ELRepo. For more information regarding ELRepo,
please visit their website at:

http://elrepo.org/

In case of questions, please resort to the RPMforge mailinglist at:

http://lists.rpmforge.net/

Kind regards,

[Ingvar Hagelund]

* Dag Wieers

Post by Dag Wieers
RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments. (...)
+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)
For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

First: This is GREAT news. Thank you so much.

Second: This may be a FAQ, but anyway; will there be much overlap
between rpmforge and epel, or will you try to avoid parallell work by
skip packages that exists in epel? (In short: Is it a goal to make
rpmforge and epel more compatible?)

(I may ask the same question about the centos repos, but we can let that
be for now.)

Ingvar

[Dag Wieers]

Hi,

RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments.

Here is a summary of changes that recently happened to RPMforge.

= RPMforge provides Red Hat Enterprise Linux 6 packages

With the advent of Red Hat Enterprise Linux 6, RPMforge provides many
packages built specifically for RHEL6.


= RPMforge now consists of more than one repository:

+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)

For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

This change can result today in unresolved dependencies that did not
happen in the past (mostly regarding perl packages). In case you have
such a problem, please report those to one of our mailinglists.

Users that in the past used RPMforge without special measures to
protect base packages (yum protectbase or priorities plugins) are
advised to enable rpmforge-extras once, to update to rfx-tagged
packages. Afterwards include only those packages with a seperate
includepkgs= statement in the .repo file.


= DKMS packages for RHEL5 have been removed

RPMforge is working closely together with ELRepo, another third-party
repository specialized in kernel modules (drivers and kernel-related
functionality). Since their kmod RPM packages are using a modern
replacement for DKMS that in many situations are superior to DKMS, we
see no need in providing DKMS packages (especially since they have not
been maintained for some time).

Users that have been using DKMS packages from RPMforge on RHEL5 are
invited to migrate to ELRepo. For more information regarding ELRepo,
please visit their website at:

http://elrepo.org/

In case of questions, please resort to the RPMforge mailinglist at:

http://lists.rpmforge.net/

Kind regards,

[Dag Wieers]

Hi,

RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments.

Here is a summary of changes that recently happened to RPMforge.

= RPMforge provides Red Hat Enterprise Linux 6 packages

With the advent of Red Hat Enterprise Linux 6, RPMforge provides many
packages built specifically for RHEL6.


= RPMforge now consists of more than one repository:

+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)

For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

This change can result today in unresolved dependencies that did not
happen in the past (mostly regarding perl packages). In case you have
such a problem, please report those to one of our mailinglists.

Users that in the past used RPMforge without special measures to
protect base packages (yum protectbase or priorities plugins) are
advised to enable rpmforge-extras once, to update to rfx-tagged
packages. Afterwards include only those packages with a seperate
includepkgs= statement in the .repo file.


= DKMS packages for RHEL5 have been removed

RPMforge is working closely together with ELRepo, another third-party
repository specialized in kernel modules (drivers and kernel-related
functionality). Since their kmod RPM packages are using a modern
replacement for DKMS that in many situations are superior to DKMS, we
see no need in providing DKMS packages (especially since they have not
been maintained for some time).

Users that have been using DKMS packages from RPMforge on RHEL5 are
invited to migrate to ELRepo. For more information regarding ELRepo,
please visit their website at:

http://elrepo.org/

In case of questions, please resort to the RPMforge mailinglist at:

http://lists.rpmforge.net/

Kind regards,

[Ingvar Hagelund]

* Dag Wieers

Post by Dag Wieers
RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments. (...)
+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)
For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

First: This is GREAT news. Thank you so much.

Second: This may be a FAQ, but anyway; will there be much overlap
between rpmforge and epel, or will you try to avoid parallell work by
skip packages that exists in epel? (In short: Is it a goal to make
rpmforge and epel more compatible?)

(I may ask the same question about the centos repos, but we can let that
be for now.)

Ingvar

[Dag Wieers]

Hi,

RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments.

Here is a summary of changes that recently happened to RPMforge.

= RPMforge provides Red Hat Enterprise Linux 6 packages

With the advent of Red Hat Enterprise Linux 6, RPMforge provides many
packages built specifically for RHEL6.


= RPMforge now consists of more than one repository:

+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)

For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

This change can result today in unresolved dependencies that did not
happen in the past (mostly regarding perl packages). In case you have
such a problem, please report those to one of our mailinglists.

Users that in the past used RPMforge without special measures to
protect base packages (yum protectbase or priorities plugins) are
advised to enable rpmforge-extras once, to update to rfx-tagged
packages. Afterwards include only those packages with a seperate
includepkgs= statement in the .repo file.


= DKMS packages for RHEL5 have been removed

RPMforge is working closely together with ELRepo, another third-party
repository specialized in kernel modules (drivers and kernel-related
functionality). Since their kmod RPM packages are using a modern
replacement for DKMS that in many situations are superior to DKMS, we
see no need in providing DKMS packages (especially since they have not
been maintained for some time).

Users that have been using DKMS packages from RPMforge on RHEL5 are
invited to migrate to ELRepo. For more information regarding ELRepo,
please visit their website at:

http://elrepo.org/

In case of questions, please resort to the RPMforge mailinglist at:

http://lists.rpmforge.net/

Kind regards,

[Dag Wieers]

Hi,

RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments.

Here is a summary of changes that recently happened to RPMforge.

= RPMforge provides Red Hat Enterprise Linux 6 packages

With the advent of Red Hat Enterprise Linux 6, RPMforge provides many
packages built specifically for RHEL6.


= RPMforge now consists of more than one repository:

+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)

For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

This change can result today in unresolved dependencies that did not
happen in the past (mostly regarding perl packages). In case you have
such a problem, please report those to one of our mailinglists.

Users that in the past used RPMforge without special measures to
protect base packages (yum protectbase or priorities plugins) are
advised to enable rpmforge-extras once, to update to rfx-tagged
packages. Afterwards include only those packages with a seperate
includepkgs= statement in the .repo file.


= DKMS packages for RHEL5 have been removed

RPMforge is working closely together with ELRepo, another third-party
repository specialized in kernel modules (drivers and kernel-related
functionality). Since their kmod RPM packages are using a modern
replacement for DKMS that in many situations are superior to DKMS, we
see no need in providing DKMS packages (especially since they have not
been maintained for some time).

Users that have been using DKMS packages from RPMforge on RHEL5 are
invited to migrate to ELRepo. For more information regarding ELRepo,
please visit their website at:

http://elrepo.org/

In case of questions, please resort to the RPMforge mailinglist at:

http://lists.rpmforge.net/

Kind regards,

[Ingvar Hagelund]

* Dag Wieers

Post by Dag Wieers
RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments. (...)
+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)
For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

First: This is GREAT news. Thank you so much.

Second: This may be a FAQ, but anyway; will there be much overlap
between rpmforge and epel, or will you try to avoid parallell work by
skip packages that exists in epel? (In short: Is it a goal to make
rpmforge and epel more compatible?)

(I may ask the same question about the centos repos, but we can let that
be for now.)

Ingvar

[Dag Wieers]

Hi,

RPMforge is a third-party repository for RHEL, CentOS and Scientific
Linux. It provides add-on RPM packages that increase functionality and
productivity for both Server and Desktop based environments.

Here is a summary of changes that recently happened to RPMforge.

= RPMforge provides Red Hat Enterprise Linux 6 packages

With the advent of Red Hat Enterprise Linux 6, RPMforge provides many
packages built specifically for RHEL6.


= RPMforge now consists of more than one repository:

+ rpmforge - packages that _do not_ replace base packages
(eg. nagios, wine, vlc, xine, mpg123, ...)
+ rpmforge-extras - newer packages that _do_ replace base packages
(eg. lftp, rsync, subversion, ...)
+ rpmforge-testing - alternative test packages
(eg. wine-1.3.x, ...)
+ rpmforge-buildtools - packages required for building RPMforge pkgs
(eg. bison, make, rpm-macros-rpmforge, ...)

For convenience, packages belonging to one of the above repositories
are tagged respectively with rf, rfx, rft and rfb distribution tags.

This change can result today in unresolved dependencies that did not
happen in the past (mostly regarding perl packages). In case you have
such a problem, please report those to one of our mailinglists.

Users that in the past used RPMforge without special measures to
protect base packages (yum protectbase or priorities plugins) are
advised to enable rpmforge-extras once, to update to rfx-tagged
packages. Afterwards include only those packages with a seperate
includepkgs= statement in the .repo file.


= DKMS packages for RHEL5 have been removed

RPMforge is working closely together with ELRepo, another third-party
repository specialized in kernel modules (drivers and kernel-related
functionality). Since their kmod RPM packages are using a modern
replacement for DKMS that in many situations are superior to DKMS, we
see no need in providing DKMS packages (especially since they have not
been maintained for some time).

Users that have been using DKMS packages from RPMforge on RHEL5 are
invited to migrate to ELRepo. For more information regarding ELRepo,
please visit their website at:

http://elrepo.org/

In case of questions, please resort to the RPMforge mailinglist at:

http://lists.rpmforge.net/

Kind regards,