[lm-sensors] Separate package for i2c tools

[lm-sensors] Separate package for i2c tools

[Jean Delvare]

Hi all,

As part of the libsensors rewrite that is ongoing, the lm-sensors
package is being reorganized. For example I already deleted all the
Linux 2.4 kernel drivers that were previously part of the package.
Another step which I'd like to take is moving the i2c tools to a
separate package.

Rationale:
* Many users of lm-sensors no longer need them, because their hardware
monitoring chip is on the LPC or PCI bus and not on the SMBus.
* Even for users of SMBus hardware monitoring chips, the i2c tools are
only needed for debugging, so most users don't need them.
* There are many other I2C devices out there (RTC, video...),
developers of drivers for these devices could make use of these tools,
but they may not even know they exist, or they know but they don't
want to bother installing the whole lm-sensors package.
* The future lm-sensors will only support 2.6 kernels, while the i2c
tools will still support older kernels.

We need to find a package name. I propose "i2c-tools". Objections?

We also need to agree on which files should be moved. Some parts of the
(current) lm-sensors package clearly belong to the new i2c tools
package: i2cdetect, i2cdump, i2cget, i2cset, ddcmon, decode-dimms.pl,
decode-edid.pl, decode-vaio.pl, decode-xeon.pl, eepromer/*, py-smbus/*,
i2c-dev.h. For some others it's not so clear.

* isadump, isaset: Not strictly sensors-specific, but not i2c-related
either. They share their command line syntax and a very small amount of
code with i2cdump. I'd rather leave them where they are.

* unhide_ICH_SMBus: Not strictly sensors-specific, but I don't think
people really need this unless they are trying to get their sensors to
work. No opinion.

* matorb/*: Last touched 8 years ago. Hmm, delete?

* mkdev.sh: Not strictly sensors-related, but the FAQ, INSTALL and
sensors-detect refer to it. It probably doesn't really matter as these
device nodes are created by udev nowadays. No opinion.

I plan to remove the dependency between sensors-detect and i2cdetect as
part of this change, otherwise we lose much of the benefit.
sensors-detect only uses i2cdetect to list the available i2c buses, it
should be easy to do the same in perl directly.

Axel, how can I create a brand new project in SVN? Do I need your help?
Is it possible to preserve the history while moving the files from one
project to another?

Thanks,
-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Separate package for i2c tools

[Axel Thimm]

[-- Attachment #1.1: Type: text/plain, Size: 872 bytes --]

On Mon, Jun 25, 2007 at 11:12:44AM +0200, Jean Delvare wrote:
> Axel, how can I create a brand new project in SVN? Do I need your help?

Not really (but see below for acls), technically it is one project, so
all you need to do is

svn mkdir my-new-project

at the top level next to lm_sensors and i2c.

The only thing that I need to do is setting up the acls in the httpd
config you want to use on that project. It can be
lm-sensors-commiters, i2c-commiters or something new.

> Is it possible to preserve the history while moving the files from one
> project to another?

Just use svn mv instead of svn rm/del and svn add. Move operations are
like copy and delete, and copy operations are crossed over when
traversing history unless you explicitely use --stop-on-copy.

See also

svn mkdir -h
svn mv -h
svn log -h
-- 
Axel.Thimm at ATrpms.net

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Separate package for i2c tools

[Jean Delvare]

Hi Axel,

On Mon, 25 Jun 2007 11:22:30 +0200, Axel Thimm wrote:
> On Mon, Jun 25, 2007 at 11:12:44AM +0200, Jean Delvare wrote:
> > Axel, how can I create a brand new project in SVN? Do I need your help?
> 
> Not really (but see below for acls), technically it is one project, so
> all you need to do is
> 
> svn mkdir my-new-project
> 
> at the top level next to lm_sensors and i2c.

This is so easy :) OK, done that.

> The only thing that I need to do is setting up the acls in the httpd
> config you want to use on that project. It can be
> lm-sensors-commiters, i2c-commiters or something new.

That would be something new: i2c-tools-commiters. This is an
essentially separate package, that could have developers with no
interest in sensors at all. And i2c-commiters is a restricted group, so
it wouldn't fit either.

BTW, how come that I was allowed to create and fill the i2c-tools
directory before you created the new group? Am I almighty or something? ;)

> > Is it possible to preserve the history while moving the files from one
> > project to another?
> 
> Just use svn mv instead of svn rm/del and svn add. Move operations are
> like copy and delete, and copy operations are crossed over when
> traversing history unless you explicitely use --stop-on-copy.

Wow, very nice.

Thanks,
-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Separate package for i2c tools

[Axel Thimm]

[-- Attachment #1.1: Type: text/plain, Size: 1562 bytes --]

Hi,

On Wed, Jun 27, 2007 at 10:18:28AM +0200, Jean Delvare wrote:
> On Mon, 25 Jun 2007 11:22:30 +0200, Axel Thimm wrote:
> > On Mon, Jun 25, 2007 at 11:12:44AM +0200, Jean Delvare wrote:
> > > Axel, how can I create a brand new project in SVN? Do I need your help?
> > 
> > Not really (but see below for acls), technically it is one project, so
> > all you need to do is
> > 
> > svn mkdir my-new-project
> > 
> > at the top level next to lm_sensors and i2c.
> 
> This is so easy :) OK, done that.
> 
> > The only thing that I need to do is setting up the acls in the httpd
> > config you want to use on that project. It can be
> > lm-sensors-commiters, i2c-commiters or something new.
> 
> That would be something new: i2c-tools-commiters. This is an
> essentially separate package, that could have developers with no
> interest in sensors at all. And i2c-commiters is a restricted group, so
> it wouldn't fit either.

OK, the group is setup.

> BTW, how come that I was allowed to create and fill the i2c-tools
> directory before you created the new group? Am I almighty or something? ;)

Every lm-sensors committer is almighty :)

> > > Is it possible to preserve the history while moving the files from one
> > > project to another?
> > 
> > Just use svn mv instead of svn rm/del and svn add. Move operations are
> > like copy and delete, and copy operations are crossed over when
> > traversing history unless you explicitely use --stop-on-copy.
> 
> Wow, very nice.
> 
> Thanks,

-- 
Axel.Thimm at ATrpms.net

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] [i2c] Separate package for i2c tools

[Jean Delvare]

Hi all,

On Mon, 25 Jun 2007 11:12:44 +0200, Jean Delvare wrote:
> As part of the libsensors rewrite that is ongoing, the lm-sensors
> package is being reorganized. For example I already deleted all the
> Linux 2.4 kernel drivers that were previously part of the package.
> Another step which I'd like to take is moving the i2c tools to a
> separate package.
> (...)
> We need to find a package name. I propose "i2c-tools". Objections?
> 
> We also need to agree on which files should be moved. Some parts of the
> (current) lm-sensors package clearly belong to the new i2c tools
> package: i2cdetect, i2cdump, i2cget, i2cset, ddcmon, decode-dimms.pl,
> decode-edid.pl, decode-vaio.pl, decode-xeon.pl, eepromer/*, py-smbus/*,
> i2c-dev.h.

OK, this is done now.

>            For some others it's not so clear.
>
> * isadump, isaset: Not strictly sensors-specific, but not i2c-related
> either. They share their command line syntax and a very small amount of
> code with i2cdump. I'd rather leave them where they are.
> 
> * unhide_ICH_SMBus: Not strictly sensors-specific, but I don't think
> people really need this unless they are trying to get their sensors to
> work. No opinion.
> 
> * matorb/*: Last touched 8 years ago. Hmm, delete?
> 
> * mkdev.sh: Not strictly sensors-related, but the FAQ, INSTALL and
> sensors-detect refer to it. It probably doesn't really matter as these
> device nodes are created by udev nowadays. No opinion.

I didn't touch these yet, so this can still be discussed.

> I plan to remove the dependency between sensors-detect and i2cdetect as
> part of this change, otherwise we lose much of the benefit.
> sensors-detect only uses i2cdetect to list the available i2c buses, it
> should be easy to do the same in perl directly.

This is done too. I even backported this change to lm-sensors/trunk, as
I am trying to keep sensors-detect in sync for now.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors