> I wonder if there could be a more simple way, i.e. putting it into a
> *.bat script and binding it to an task icon.
>
> I am thinking of something in this sense:
>
> P:/cygwin/bin/ash --exec /bin/rebaseall
>
> As a longterm Linux user I have few experience with windows scripts.
> Would be nice to
> I'd beg to differ; I'd suggest it is, as suggested by the OP,
> actually quite a common use. You only have to look at the use of
> say perl and you will have users quite regularly compiling their
> own DLL's as they install modules via CPAN, and this is quite painful
> due to all the issues it ca
On Sun, Sep 19, 2010 at 03:52:56AM +0100, Steven Hartland wrote:
>- Original Message -
>From: "Christopher Faylor"
>
>>>What I suggest isn't that usefull when you think to base all
>>>DLL that have been installed by setup.exe. It becomes usefull in the
>>>moment the user starts to compile
- Original Message -
From: "Christopher Faylor"
What I suggest isn't that usefull when you think to base all
DLL that have been installed by setup.exe. It becomes usefull in the
moment the user starts to compile his own DLL especially if he used
scripts to control compilation. To compil
On Sun, Sep 19, 2010 at 12:43:17AM +0200, Al wrote:
>On Sat, Sep 18, 2010 at 05:48:07PM -0400, Christopher Faylor wrote:
>>>scripts to control compilation. To compile somethng is a typical use
>>>of cygwin.
>>
>> No, it really isn't.
>
>I quote wikipedia:
>
>Cygwin is used heavily for porting many
>>scripts to control compilation. To compile somethng is a typical use
>>of cygwin.
>
> No, it really isn't.
I quote wikipedia:
Cygwin is used heavily for porting many popular pieces of software to
the Windows platform. It is used to compile Sun Java, OpenOffice.org,
and even server software, lik
On Sat, Sep 18, 2010 at 08:36:28PM +0200, Al wrote:
>>> A second thought. I wonder if reabaseall could be improved to run from
>>> within bash, without the need to close down all running windows. Then
>>> it could even be included into build scripts to be run after each
>>> build.
>>
>> No, because
>> A second thought. I wonder if reabaseall could be improved to run from
>> within bash, without the need to close down all running windows. Then
>> it could even be included into build scripts to be run after each
>> build.
>
> No, because the DLLs used by bash are OFTEN the ones that actually DO
>
> If that is the only doc to point to, then you are right.
> Alternatively, the recent archives might point to how hard existing docs
> are to find.
Good doc is availble. Unfortunatly it is badly linked.
http://www.tishler.net/jason/software/rebase/rebase-2.4.2.README
It's not the first thing
> >-bash-3.2$ /bin/rebaseall --help
> >rebaseall: only ash or dash processes are allowed during rebasing
> >Exit all Cygwin processes and stop all Cygwin services.
> >Execute ash (or dash) from Start/Run... or a cmd or command
window.
> >Execute '/bin/rebaseall' from ash (or dash).
> >
On Fri, Sep 17, 2010 at 08:49:04PM +0200, Al wrote:
>>
>> This discussion seems to boil down to "Someone should add words about
>> rebaseall to the FAQ".
>>
>
>If words to the FAQ, then:
>
>1.) a matching header
>2.) including link to the readme
>3.) including the famous error messages people enter
On Fri, Sep 17, 2010 at 11:48:47AM -0700, Bill Ross wrote:
>> This discussion seems to boil down to "Someone should add words about
>> rebaseall to the FAQ".
>
>-bash-3.2$ /bin/rebaseall --help
>rebaseall: only ash or dash processes are allowed during rebasing
>Exit all Cygwin processes and sto
>
> This discussion seems to boil down to "Someone should add words about
> rebaseall to the FAQ".
>
If words to the FAQ, then:
1.) a matching header
2.) including link to the readme
3.) including the famous error messages people enter into the search machines:
*** fatal error - unable to remap
> This discussion seems to boil down to "Someone should add words about
> rebaseall to the FAQ".
-bash-3.2$ /bin/rebaseall --help
rebaseall: only ash or dash processes are allowed during rebasing
Exit all Cygwin processes and stop all Cygwin services.
Execute ash (or dash) from Start/Run..
On Fri, Sep 17, 2010 at 08:01:23PM +0200, Al wrote:
>> I guess for many people cygwin is their first contact with a *NIX like
>> environment, but given your previous knowledge in Linux, it could also
>> have been and option to inspect the package contents:
>>
>> cygcheck -l rebase
>>
>
>It's not on
On 9/17/2010 1:38 PM, Al wrote:
Hi,
I appreciate you take the time to contribute all that information.
Hope it is not only red by me.
Now, surely that is a lot of hunting around -- but I can only assume
that many people did so, since you are apparently the first person to
fail to locate the d
On Fri, Sep 17, 2010 at 08:01:23PM +0200, Al wrote:
> > I guess for many people cygwin is their first contact with a *NIX like
> > environment, but given your previous knowledge in Linux, it could also
> > have been and option to inspect the package contents:
> >
> > cygcheck -l rebase
>
> It's no
> I guess for many people cygwin is their first contact with a *NIX like
> environment, but given your previous knowledge in Linux, it could also
> have been and option to inspect the package contents:
>
> cygcheck -l rebase
>
It's not only that many people have in Cygwin their first contact with
On Fri, Sep 17, 2010 at 07:38:03PM +0200, Al wrote:
> Hi,
Hello,
> It's familiar that regular programs have a doc, man etc. It's also
> familiar that small maintenance scripts don't have. Even your posting
> has more lines the he rebaseall script itself. So you wouldn't really
> follow the search
Hi,
I appreciate you take the time to contribute all that information.
Hope it is not only red by me.
>
> Now, surely that is a lot of hunting around -- but I can only assume
> that many people did so, since you are apparently the first person to
> fail to locate the documentation when faced with
On 9/17/2010 12:18 PM, Al wrote:
>>
>> And it invites casual use without understanding the what and why. This
>> means
>> more people using it for no reason and more problems using it when it is
>> needed because people don't understand the requirements to make it work
>> (i.e. *nobody* will read
>
> And it invites casual use without understanding the what and why. This
> means
> more people using it for no reason and more problems using it when it is
> needed because people don't understand the requirements to make it work
> (i.e. *nobody* will read the readme... wait, there's a readme? ;
On 9/17/2010 10:50 AM, Charles Wilson wrote:
On 9/17/2010 10:39 AM, Al wrote:
A second thought. I wonder if reabaseall could be improved to run from
within bash, without the need to close down all running windows. Then
it could even be included into build scripts to be run after each
build.
No
On 9/17/2010 10:39 AM, Al wrote:
> A second thought. I wonder if reabaseall could be improved to run from
> within bash, without the need to close down all running windows. Then
> it could even be included into build scripts to be run after each
> build.
No, because the DLLs used by bash are OFTEN
A second thought. I wonder if reabaseall could be improved to run from
within bash, without the need to close down all running windows. Then
it could even be included into build scripts to be run after each
build.
Assuming that those DLL which are up and running typically don't need
to be rebased,
25 matches
Mail list logo
