Hi there,
On Mon, 19 Oct 2009 Chris Cormie wrote:
> I am working on a Cygwin package manager with an interface
> resembling apt-get.
This is the package that I've been dreaming of for years!
> It would be great if some folks tried out the initial release and
> provided me w
Correction: setup doesn't require Cygwin to be closed if not working on
core packages. That makes sense.
Chris.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http:/
There's no maturity requirement as such. For a package such as cyg-apt that
doesn't exist in other distros, you have to get 5 positive votes from current
package maintainers. A clear explanation of what cyg-apt does that setup
doesn't, would probably go a long way towards that.
Thanks for that
> > On first look, it seems good. Would you consider packaging it as a
> Cygwin
> > package? You'd get more people using it that way.
> >
> > If you haven't maintained a Cygwin package before, it wouldn't be
> much work
> > to get this one going, since it's so simple. I don't think I'd wa
> On first look, it seems good. Would you consider packaging it as a
Cygwin
> package? You'd get more people using it that way.
>
> If you haven't maintained a Cygwin package before, it wouldn't be
much work
> to get this one going, since it's so simple. I don't think I'd want to
> maintain
Jacob Jacobson wrote:
> Chris Cormie wrote:
>> Hi,
>>
>> I am working on a Cygwin package manager with an interface resembling
>> apt-get.
>> It's still a work in progress, but functional (commands below.)
>> http://code.google.com/p/cyg-apt/
>
>
> I am working on a Cygwin package manager with an interface resembling
> apt-get.
> It's still a work in progress, but functional (commands below.)
> http://code.google.com/p/cyg-apt/
>
> It would be great if some folks tried out the initial release and
> provided
Chris Cormie wrote:
Hi,
I am working on a Cygwin package manager with an interface resembling
apt-get.
It's still a work in progress, but functional (commands below.)
http://code.google.com/p/cyg-apt/
[cyg-apt-1.0.4-1$:530] ./cyg-apt setup
cyg-apt: creating /c/home//.cyg-apt.
getting
Hi,
I am working on a Cygwin package manager with an interface resembling
apt-get.
It's still a work in progress, but functional (commands below.)
http://code.google.com/p/cyg-apt/
It would be great if some folks tried out the initial release and
provided me with some feedback.
C
On Sun, Feb 15, 2009 at 02:35:25AM +0800, Brant Young wrote:
>On Sat, Feb 14, 2009 at 5:59 PM, Corinna Vinschen
>>We have loads of suggestions for changes to Cygwin or setup.exe.
>
>Where can I get the these suggestions ?
The mailing list archives.
cgf
--
Unsubscribe info: http://cygwin.com
On Sat, Feb 14, 2009 at 5:59 PM, Corinna Vinschen
wrote:
> ... but it would have been much more helpful to put the time into hacking up
> setup.exe, instead of creating another, competing installer.
I'll try to write a "common setup engine wrapper" to reuse current
setup.exe code, and try to spl
On Feb 13 20:29, Lee D.Rothstein wrote:
> I found Brant & Warren Young and Dave Korn, et al's comments
> about a possible conjoined 'setup', and the unfortunately
> named (& soon to be renamed -- TYVM), 'cygwine', and the
> requirements thereto (;-)), to be right to the point.
It's nice that someb
Warren Young wrote:
Brant Young wrote:
I have launched a opensource project -- CygWine ( a cygwin package
management utility, project homepage: http://cygwine.googlecode.com )
My initial thought on seeing the name is that it was a port of Wine to
Cygwin, which would be tres silly.
It's got my
I found Brant & Warren Young and Dave Korn, et al's comments
about a possible conjoined 'setup', and the unfortunately
named (& soon to be renamed -- TYVM), 'cygwine', and the
requirements thereto (;-)), to be right to the point.
I would like to suggest two new features for the
setup/command line
2009/2/12 Yitzchak Scott-Thoennes:
> I'd rather see the common code put into a library (and available in
> both cygwin and mingw flavors). Then it would be pretty easy to
> have a Cygwin::Setup perl extension and command line tools using it.
> (Substitute your other glue language of choice as desi
> On Thu, Feb 12, 2009 at 12:37 PM, Warren Young wrote:
> I had that exact same thought. If it can't be merged into the standard
> setup.exe, I would at least recommend a different name.
Everyone hates the name :-)
It seems I should change the name in the next major release.
Regards,
Brant
> I'm taking a quick browse through the code. I see that you've based it on
> chunks of the core setup.exe code, somewhat refactored and restructured.
Yes, a lot of non-UI code were migrated from setup.exe.
> I wonder ... do you think that would be practical?
I think you made a wonderful propo
Hi brother, thanks for all you reviews and suggestions.
I like yum and apt-get too.
CygWine still in somewhat early age, I will consider your proposals
seriously during the next release.
Regards,
Brant
On Fri, Feb 13, 2009 at 1:37 AM, Warren Young wrote:
> Brant Young wrote:
>>
>> I have laun
I'd rather see the common code put into a library (and available in
both cygwin and mingw flavors). Then it would be pretty easy to
have a Cygwin::Setup perl extension and command line tools using it.
(Substitute your other glue language of choice as desired.)
On Thu, February 12, 2009 10:17 am,
As a layman (not a cygwin developer or anything), I have to say this
looks really great. The current setup.exe program is certainly (and
almost exclusively) _functional_, this kind of UI is really the next
step.
One thing that could use a major rethink, and seems to be carried over
from the curre
On Thu, 12 Feb 2009, Mark J. Reed wrote:
On Thu, Feb 12, 2009 at 12:37 PM, Warren Young wrote:
Brant Young wrote:
I have launched a opensource project -- CygWine ( a cygwin package
management utility, project homepage:
http://cygwine.googlecode.com )
My initial thought on seeing the name is t
Dave Korn wrote:
I'm taking a quick browse through the code. I see that you've based it on
chunks of the core setup.exe code, somewhat refactored and restructured. I
wonder if we couldn't merge the two codebases, in such a way that there's one
common 'setup engine' with a couple of alternati
On Thu, Feb 12, 2009 at 12:37 PM, Warren Young wrote:
> Brant Young wrote:
You two aren't related, are you? :)
>> I have launched a opensource project -- CygWine ( a cygwin package
>> management utility, project homepage: http://cygwine.googlecode.com )
>
> My initial thought on seeing the name i
Brant Young wrote:
> Hi everyone,
>
> I have launched a opensource project -- CygWine ( a cygwin package
> management utility, project homepage: http://cygwine.googlecode.com )
>
> CygWine 1.0 beta was just released, you can download the executable
> and browse screenshots at http://cygwine.googl
Brant Young wrote:
I have launched a opensource project -- CygWine ( a cygwin package
management utility, project homepage: http://cygwine.googlecode.com )
My initial thought on seeing the name is that it was a port of Wine to
Cygwin, which would be tres silly.
We don't really need two diff
Hi everyone,
I have launched a opensource project -- CygWine ( a cygwin package
management utility, project homepage: http://cygwine.googlecode.com )
CygWine 1.0 beta was just released, you can download the executable
and browse screenshots at http://cygwine.googlecode.com.
Compared to cygwin of
26 matches
Mail list logo
