Forrest, I habitually build Csound with as many features as possible
on Ubuntu 12.04. I do this because I compose on both Windows and
Linux, and I want my Linux system to have the same features as my
Windows system (I'm the maintainer of the Windows build and the
Windows installer).

I use CMake for building on Linux. I'm the original developer of the
SCons build system, and I've done a small amount of maintenance on the
CMake system.

So, if you have any questions about building on Linux, please feel
free to ask me on or off the list.

I don't know that much about the Debian package system. Nevertheless,
I do have some suggestions about maintaining the Csound packages.

First, I think that the future maintainability of Csound will be
enhanced if all changes to Csound source code or the Csound build
system that are required for the Debian packages are maintained in the
regular Csound GIT repository.

Second, I also think that the future maintainability of Csound will be
enhanced if everything required to create the Debian packages is
included as targets in the regular CMake build files. I don't know how
easy or hard that might be, but I am available to help.

And third, we have a Python "install" script that I think should be
replaced with a target in the existing CMake system that does the same
job. This should probably create the same files in the same places as
would be found in the package data.tar file.

Regards,
Mike


On Tue, Jun 5, 2012 at 3:28 AM, Victor Lazzarini
 wrote:
> I think you should ask John ffitch then to add you as a developer on
> sourceforge, which will help things too in terms of doing the Debian
> packages.
>
>
> Victor Lazzarini
>
>
>
> Forrest Cahoon  wrote:
>
>
> On Mon, Jun 4, 2012 at 1:57 PM, Felipe Sateler  wrote:
>> Hi all,
>>
>> My free time has become reduced lately, and I think I won't get more
>> in the foreseeable future. This has meant that I have less time for
>> maintaining csound (and qutecsound) in debian. Therefore, I'm asking
>> for help with maintaining the package within the Debian Multimedia
>> Team. I will continue to work on the package as time permits, and can
>> help with any issues that may arise.
>>
>> Packaging is mostly about:
>> 1. Makefile scripting, so knowledge of make is useful.
>> 2. *Some* knowledge of how the actual software works and its internals
>> (the more the better but being a full C wizard is not required, you
>> can ask for help when the need arises).
>> 3. Managing bug reports (this doesn't mean actually solving them.
>> Forwarding them here when appropriate is usually enough).
>> 4. Communicating with upstream (that is, keep in touch in this list).
>> 5. And most importantly, actually use csound and debian (or at least
>> ubuntu) ;)
>>
>>
>> If anybody wants to help, please let me know. I have not started
>> packaging the latest csound 5.17.x release, so we can use that as a
>> training exercise to get familiar with the packaging and tools.
>
> I'll do it! Not only do I meet all those qualifications, I've been
> spending most of my time recently trying to get csound working on
> debian -- might be a little more productive of me to do that for
> everyone instead of just myself.
>
> Forrest
>
>> Saludos,
>> Felipe Sateler
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi all,

First of all, apparently my message read as if I was retiring from
maintaining the debian package. That is not so! I just have reduced
time, so getting co-maintainers would make the debian package better.

Forrest Cahoon  wrote:
> I'll do it! Not only do I meet all those qualifications, I've been
> spending most of my time recently trying to get csound working on
> debian -- might be a little more productive of me to do that for
> everyone instead of just myself.

Great! First, we need to clear some bureaucracy. Please go to:

http://alioth.debian.org/projects/pkg-multimedia

Create an account and join that team, and then subscribe to the
pkg-multimedia-maintainers mailing list (that list is where all the
bug reports go).

On Tue, Jun 5, 2012 at 8:29 AM, Michael Gogins  wrote:
> Forrest, I habitually build Csound with as many features as possible
> on Ubuntu 12.04. I do this because I compose on both Windows and
> Linux, and I want my Linux system to have the same features as my
> Windows system (I'm the maintainer of the Windows build and the
> Windows installer).
>
> I use CMake for building on Linux. I'm the original developer of the
> SCons build system, and I've done a small amount of maintenance on the
> CMake system.
>
> So, if you have any questions about building on Linux, please feel
> free to ask me on or off the list.
>
> I don't know that much about the Debian package system. Nevertheless,
> I do have some suggestions about maintaining the Csound packages.

Please do them anyway ;)

>
> First, I think that the future maintainability of Csound will be
> enhanced if all changes to Csound source code or the Csound build
> system that are required for the Debian packages are maintained in the
> regular Csound GIT repository.

This might or might not be actually the case. One of my duties as
maintainer is to forward all relevant patches here (usually I even do
the changes here first and then backport the patch). The remaining
patches are all mostly debian-specific. See [1] for all the patches we
currently apply.
I'm not really sure if there are any more synergies by using the same
repository. Keep in mind that we value keeping as close as possible to
released tarballs.

[1] http://patch-tracker.debian.org/package/csound/1:5.17.6~dfsg-3

>
> Second, I also think that the future maintainability of Csound will be
> enhanced if everything required to create the Debian packages is
> included as targets in the regular CMake build files. I don't know how
> easy or hard that might be, but I am available to help.

It mostly is. The debian build script is basically a Makefile that
calls cmake, and then moves some stuff around (eg, the extract
executable is renamied as csound_extract because there is another
package that includes the same binary).
Most of that extra stuff being done is to comply with debian policy,
I'm not quite sure if other linux distributions follow the same
standards.

>
> And third, we have a Python "install" script that I think should be
> replaced with a target in the existing CMake system that does the same
> job. This should probably create the same files in the same places as
> would be found in the package data.tar file.

We are using the cmake install target.

-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks for this information. I am processing it...

Regards,
Mike

On Tue, Jun 5, 2012 at 9:49 AM, Felipe Sateler  wrote:
> Hi all,
>
> First of all, apparently my message read as if I was retiring from
> maintaining the debian package. That is not so! I just have reduced
> time, so getting co-maintainers would make the debian package better.
>
> Forrest Cahoon  wrote:
>> I'll do it! Not only do I meet all those qualifications, I've been
>> spending most of my time recently trying to get csound working on
>> debian -- might be a little more productive of me to do that for
>> everyone instead of just myself.
>
> Great! First, we need to clear some bureaucracy. Please go to:
>
> http://alioth.debian.org/projects/pkg-multimedia
>
> Create an account and join that team, and then subscribe to the
> pkg-multimedia-maintainers mailing list (that list is where all the
> bug reports go).
>
> On Tue, Jun 5, 2012 at 8:29 AM, Michael Gogins  wrote:
>> Forrest, I habitually build Csound with as many features as possible
>> on Ubuntu 12.04. I do this because I compose on both Windows and
>> Linux, and I want my Linux system to have the same features as my
>> Windows system (I'm the maintainer of the Windows build and the
>> Windows installer).
>>
>> I use CMake for building on Linux. I'm the original developer of the
>> SCons build system, and I've done a small amount of maintenance on the
>> CMake system.
>>
>> So, if you have any questions about building on Linux, please feel
>> free to ask me on or off the list.
>>
>> I don't know that much about the Debian package system. Nevertheless,
>> I do have some suggestions about maintaining the Csound packages.
>
> Please do them anyway ;)
>
>>
>> First, I think that the future maintainability of Csound will be
>> enhanced if all changes to Csound source code or the Csound build
>> system that are required for the Debian packages are maintained in the
>> regular Csound GIT repository.
>
> This might or might not be actually the case. One of my duties as
> maintainer is to forward all relevant patches here (usually I even do
> the changes here first and then backport the patch). The remaining
> patches are all mostly debian-specific. See [1] for all the patches we
> currently apply.
> I'm not really sure if there are any more synergies by using the same
> repository. Keep in mind that we value keeping as close as possible to
> released tarballs.
>
> [1] http://patch-tracker.debian.org/package/csound/1:5.17.6~dfsg-3
>
>>
>> Second, I also think that the future maintainability of Csound will be
>> enhanced if everything required to create the Debian packages is
>> included as targets in the regular CMake build files. I don't know how
>> easy or hard that might be, but I am available to help.
>
> It mostly is. The debian build script is basically a Makefile that
> calls cmake, and then moves some stuff around (eg, the extract
> executable is renamied as csound_extract because there is another
> package that includes the same binary).
> Most of that extra stuff being done is to comply with debian policy,
> I'm not quite sure if other linux distributions follow the same
> standards.
>
>>
>> And third, we have a Python "install" script that I think should be
>> replaced with a target in the existing CMake system that does the same
>> job. This should probably create the same files in the same places as
>> would be found in the package data.tar file.
>
> We are using the cmake install target.
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net