Re: cygport limitations

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

On Jun 21 13:50, Yaakov (Cygwin/X) wrote:
> On 2013-06-21 13:10, Warren Young wrote:
> >On 6/21/2013 12:05, Warren Young wrote:
> >>With cygport, you wouldn't even need to provide sources.  We could email
> >>in the new cygport file instead of an RFU.
> >
> >...and patches.
> >
> >...and customized .hint files, if needed.
> >
> >Yeah, I guess sending the .src.tar.bz2 probably is effectively required.
> 
> No, it's not.  IIUC, the eventual goal should be something that
> looks like Ports git:
> 
> http://cygwin-ports.git.sourceforge.net/
> 
> together with a buildbot.  Package maintainers would then commit
> their changes to a package's repo, which would then trigger a
> post-commit hook that would cause the package to be built with those
> changes.

Yes, that sounds good.  The last discussions in my dept about setting up
a build system are long gone, so we have to start anew.  This will take
some time (think unsavory things like budgets and so on...), but I'll
keep on it.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple