--8<---cut here---start->8---
wget="wget -rxnH http://cygwin.stromeko.net/noarch/release";
$wget/_autorebase-001000-1-src.tar.xz
$wget/_autorebase-001000-1.tar.xz
$wget/setup.hint
--8<---cut here---end--->8---
Requirements b
On 12/13/2014 10:56 AM, Achim Gratz wrote:
--8<---cut here---start->8---
wget="wget -rxnH http://cygwin.stromeko.net/noarch/release";
$wget/_autorebase-001000-1-src.tar.xz
$wget/_autorebase-001000-1.tar.xz
$wget/setup.hint
--8<---cut here--
On 12/13/2014 10:56 AM, Achim Gratz wrote:
Requirements before deployment:
- all autodep stuff referring to _autorebase must be removed
- setup.exe version 2.858 or later must be used
Notes:
There will be no ITP for _incautorebase since Corinna wanted a
replacement for _autorebase instead.
D
Ken Brown writes:
> 1. Shouldn't you have removed the following line from rebase_do?
>
> peflags ${verbose} -d0 -t0 -T "${g}"
That isn't redundant and has nothing to do with the stuff in peflags_do,
although I don't remember exactly what the problem was that was resolved
by this. The current
Packages rebuilt with cygport including the changes discussed with Ken
and pre-compiled setup.exe files added.
--8<---cut here---start->8---
cygwin=http://cygwin.stromeko.net/
wget $cygwin/noarch/release/_autorebase/_autorebase-001000-1-src.tar.xz
wget $cygwin/
On 12/14/2014 3:56 AM, Achim Gratz wrote:
Packages rebuilt with cygport including the changes discussed with Ken
and pre-compiled setup.exe files added.
--8<---cut here---start->8---
cygwin=http://cygwin.stromeko.net/
wget $cygwin/noarch/release/_autorebase/_
Ken Brown writes:
> I just noticed a couple of things about the base address. First, you
> have a typo in line 4 of rebaselst (missing 'd').
I'll fix that before the actual release. Unless someone defines
BaseAddress in the environment this doesn't poase a problem, though.
> Second, you use a d
On 12/14/2014 12:52 PM, Achim Gratz wrote:
Ken Brown writes:
I just noticed a couple of things about the base address. First, you
have a typo in line 4 of rebaselst (missing 'd').
I'll fix that before the actual release. Unless someone defines
BaseAddress in the environment this doesn't poas
Ken Brown writes:
> The changes look good, and it works fine on an existing installation.
> But there's a problem with a new installation. The autorebase
> postinstall script seems to hang in one of the calls to "find", which
> I finally killed through the Task Manager. /var/log/setup.log.full is
On 12/14/2014 3:48 PM, Achim Gratz wrote:
Ken Brown writes:
The changes look good, and it works fine on an existing installation.
But there's a problem with a new installation. The autorebase
postinstall script seems to hang in one of the calls to "find", which
I finally killed through the Task
On Dec 13 23:06, Achim Gratz wrote:
> Ken Brown writes:
> > 1. Shouldn't you have removed the following line from rebase_do?
> >
> > peflags ${verbose} -d0 -t0 -T "${g}"
>
> That isn't redundant and has nothing to do with the stuff in peflags_do,
> although I don't remember exactly what the pr
On Dec 14 18:52, Achim Gratz wrote:
> Ken Brown writes:
> > I just noticed a couple of things about the base address. First, you
> > have a typo in line 4 of rebaselst (missing 'd').
>
> I'll fix that before the actual release. Unless someone defines
> BaseAddress in the environment this doesn't
Corinna Vinschen writes:
> On Dec 13 23:06, Achim Gratz wrote:
>> Ken Brown writes:
>> > 1. Shouldn't you have removed the following line from rebase_do?
>> >
>> > peflags ${verbose} -d0 -t0 -T "${g}"
>>
>> That isn't redundant and has nothing to do with the stuff in peflags_do,
>> although I
Corinna Vinschen writes:
> The change is required. The base address 0x4: is a convention
> which has been introduced to get reliable memory layout on x86_64. All
> of Cygwin's memory allocations, be it thread stack, executable and DLL
> base addresses, heap address, or mmap's with NULL ad
On Dec 15 18:20, Achim Gratz wrote:
> Corinna Vinschen writes:
> > The change is required. The base address 0x4: is a convention
> > which has been introduced to get reliable memory layout on x86_64. All
> > of Cygwin's memory allocations, be it thread stack, executable and DLL
> > base a
On Dec 13 16:56, Achim Gratz wrote:
>
> --8<---cut here---start->8---
> wget="wget -rxnH http://cygwin.stromeko.net/noarch/release";
> $wget/_autorebase-001000-1-src.tar.xz
> $wget/_autorebase-001000-1.tar.xz
> $wget/setup.hint
> --8<---cut here-
On 12/16/2014 8:23 AM, Corinna Vinschen wrote:
What would be most helpful is to get a piece of documentation for us
maintainers how to use the new _autorebase facility, sent with a fat
HEADSUP subject, and which we can ideally add to setup.html.
More importantly, maintainers need to be told abo
On Dec 16 16:11, Ken Brown wrote:
> On 12/16/2014 8:23 AM, Corinna Vinschen wrote:
> >What would be most helpful is to get a piece of documentation for us
> >maintainers how to use the new _autorebase facility, sent with a fat
> >HEADSUP subject, and which we can ideally add to setup.html.
>
> Mor
On Dec 17 10:39, Corinna Vinschen wrote:
> On Dec 16 16:11, Ken Brown wrote:
> > On 12/16/2014 8:23 AM, Corinna Vinschen wrote:
> > >What would be most helpful is to get a piece of documentation for us
> > >maintainers how to use the new _autorebase facility, sent with a fat
> > >HEADSUP subject, a
On 12/17/2014 4:52 AM, Corinna Vinschen wrote:
On Dec 17 10:39, Corinna Vinschen wrote:
On Dec 16 16:11, Ken Brown wrote:
On 12/16/2014 8:23 AM, Corinna Vinschen wrote:
What would be most helpful is to get a piece of documentation for us
maintainers how to use the new _autorebase facility, sen
Corinna Vinschen writes:
> Oh, and there's something else very important. The new technique
> requires the users to update setup.exe, otherwise they will get
> problems. We can't do much for people ignoring the "this setup.ini has
> been created by a newer setup version" message in setup itself,
On Dec 17 18:01, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Oh, and there's something else very important. The new technique
> > requires the users to update setup.exe, otherwise they will get
> > problems. We can't do much for people ignoring the "this setup.ini has
> > been created by a
Corinna Vinschen writes:
> That should be fine, given the rather short list of affected maintainers:
>
> octave Marco Atzeri
> perl Reini Urban/Achim Gratz ?!?
> php Yaakov Selkowitz
> python Jason Tishler/Yaakov Selkowitz
> RMarco Atzeri
> ruby Yaakov Selkowitz
Reini? Jason?
Three weeks without reply is a long time... :}
Any input?
On Dec 17 19:05, Achim Gratz wrote:
> Corinna Vinschen writes:
> > That should be fine, given the rather short list of affected maintainers:
> >
> > octave Marco Atzeri
> > perl Reini Urban/Achim Gratz ?!?
> >
Corinna,
On Wed, Jan 07, 2015 at 05:09:50PM +0100, Corinna Vinschen wrote:
> Reini? Jason?
>
> Three weeks without reply is a long time... :}
>
> Any input?
>
> On Dec 17 19:05, Achim Gratz wrote:
> > Corinna Vinschen writes:
> > > That should be fine, given the rather short list of affected
>
Hi Jason,
I'm glad to read from you!
On Jan 8 21:32, Jason Tishler wrote:
> Corinna,
>
> On Wed, Jan 07, 2015 at 05:09:50PM +0100, Corinna Vinschen wrote:
> > Reini? Jason?
> >
> > Three weeks without reply is a long time... :}
> >
> > Any input?
> >
> > On Dec 17 19:05, Achim Gratz wrote:
On Jan 7 17:09, Corinna Vinschen wrote:
> Reini? Jason?
>
>
> Three weeks without reply is a long time... :}
>
> Any input?
>
>
> On Dec 17 19:05, Achim Gratz wrote:
> > Corinna Vinschen writes:
> > > That should be fine, given the rather short list of affected maintainers:
> > >
> > > oct
On 1/14/2015 10:40 AM, Corinna Vinschen wrote:
On Jan 7 17:09, Corinna Vinschen wrote:
Reini? Jason?
Three weeks without reply is a long time... :}
Any input?
On Dec 17 19:05, Achim Gratz wrote:
Corinna Vinschen writes:
That should be fine, given the rather short list of affected mainta
On Jan 14 10:50, Marco Atzeri wrote:
> On 1/14/2015 10:40 AM, Corinna Vinschen wrote:
> >On Jan 7 17:09, Corinna Vinschen wrote:
> >>Reini? Jason?
> >>
> >>
> >>Three weeks without reply is a long time... :}
> >>
> >>Any input?
> >>
> >>
> >>On Dec 17 19:05, Achim Gratz wrote:
> >>>Corinna Vinsch
Corinna Vinschen writes:
> AFAIU, you just have to provide a per-package file defining the path
> to your dynamic libs. I just unpacked
> http://cygwin.stromeko.net/noarch/release/_autorebase/_autorebase-001000-1.tar.xz
> and it contains files under etc/rebase/dynpath.d/ called R and octave:
>
>
On Jan 14 18:00, Achim Gratz wrote:
> Corinna Vinschen writes:
> > AFAIU, you just have to provide a per-package file defining the path
> > to your dynamic libs. I just unpacked
> > http://cygwin.stromeko.net/noarch/release/_autorebase/_autorebase-001000-1.tar.xz
> > and it contains files under et
Corinna Vinschen writes:
>> BTW, do we want to keep these files in /etc or move to /var/lib? Both
>> Ken and I interpret the LSB/FSH document as recommending /var/lib as the
>> place to put such things. We could of course do that later on (there's
>> other stuff in /etc that would fall under that
On Wed, 2014-12-17 at 18:16 +0100, Corinna Vinschen wrote:
> On Dec 17 18:01, Achim Gratz wrote:
> > In fact if we do that, I'd like to require either new releases for the
> > packages using /etc/rebase/dynpath.d or alternatively that they get an
> > additional package that drops just this file (if
Yaakov Selkowitz writes:
> Some of these -- php and python at least -- do not have separate 'site'
> and 'vendor' extension directories, so adding a directory entry for
> these would pick up DLLs that are already registered with setup's
> database. How would you avoid duplicates (and hence wasted
On Jan 14 19:04, Achim Gratz wrote:
> Yaakov Selkowitz writes:
> > Some of these -- php and python at least -- do not have separate 'site'
> > and 'vendor' extension directories, so adding a directory entry for
> > these would pick up DLLs that are already registered with setup's
> > database. How
Here's the new version that places its files into /var instead of /etc
as per our previous discussion.
The control files that belong to other packages (for rebasing of dynamic
objects) and go into /var/lib/rebase/dynpath.d have been split out each
into their own package for the maintainers of thos
On Jan 17 11:05, Achim Gratz wrote:
> Here's the new version that places its files into /var instead of /etc
> as per our previous discussion.
>
> The control files that belong to other packages (for rebasing of dynamic
> objects) and go into /var/lib/rebase/dynpath.d have been split out each
> in
Guys, ping?
On Jan 19 09:53, Corinna Vinschen wrote:
> On Jan 17 11:05, Achim Gratz wrote:
> > Here's the new version that places its files into /var instead of /etc
> > as per our previous discussion.
> >
> > The control files that belong to other packages (for rebasing of dynamic
> > objects) a
Marco, Achim, Yaakov? Anybody of you here?
I mean, hey, how are we going to go forward if nobody even bothers to
reply? :(
On Jan 20 21:29, Corinna Vinschen wrote:
> On Jan 19 09:53, Corinna Vinschen wrote:
> > On Jan 17 11:05, Achim Gratz wrote:
> > > Here's the new version that places its
On 1/22/2015 6:21 PM, Corinna Vinschen wrote:
Marco, Achim, Yaakov? Anybody of you here?
I looked on the octave , and I don't think we
need a autorebase package, as the default
location is a tree under user HOME.
Moreover I am already packing anything that build on cygwin.
I need to look at
Hi Marco,
On Jan 22 18:44, Marco Atzeri wrote:
> On 1/22/2015 6:21 PM, Corinna Vinschen wrote:
> >
> >Marco, Achim, Yaakov? Anybody of you here?
> >
>
> I looked on the octave , and I don't think we
> need a autorebase package, as the default
> location is a tree under user HOME.
> Moreover I am
On 1/22/2015 6:52 PM, Corinna Vinschen wrote:
Hi Marco,
On Jan 22 18:44, Marco Atzeri wrote:
On 1/22/2015 6:21 PM, Corinna Vinschen wrote:
Marco, Achim, Yaakov? Anybody of you here?
I looked on the octave , and I don't think we
need a autorebase package, as the default
location is a tre
On Jan 22 19:04, Marco Atzeri wrote:
>
>
> On 1/22/2015 6:52 PM, Corinna Vinschen wrote:
> >Hi Marco,
> >
> >On Jan 22 18:44, Marco Atzeri wrote:
> >>On 1/22/2015 6:21 PM, Corinna Vinschen wrote:
> >>>
> >>>Marco, Achim, Yaakov? Anybody of you here?
> >>>
> >>
> >>I looked on the octave , and I
On 1/22/2015 8:33 PM, Corinna Vinschen wrote:
On Jan 22 19:04, Marco Atzeri wrote:
I have no objections to make a octave_autorebase-001001-1.tar.xz
anyway when the new autorebase is in place.
I'm not exactly sure now, but I thought the idea was that the
PACKAGE_autorebase packages are alr
Corinna Vinschen writes:
> What about the perl_autorebase package? Are you going to push this
> into the perl stuff?
For the moment I'd use a separate package and an edited setup.hint, any
new Perl release will likely have it included into the perl-base
package. But the packaging for future Perl
Corinna Vinschen writes:
> Marco, Achim, Yaakov? Anybody of you here?
>
>
> I mean, hey, how are we going to go forward if nobody even bothers to
> reply? :(
I just came back from a business trip halfway around the world. This
list is still blocked when trying to reply from Gmane, so I usually
Marco Atzeri writes:
> I looked on the octave , and I don't think we
> need a autorebase package, as the default
> location is a tree under user HOME.
> Moreover I am already packing anything that build on cygwin.
Good, then just drop the file and be done with it.
Regards,
Achim.
--
+<[Q+ Matri
Corinna Vinschen writes:
>> It will be eventually "/usr/lib/octave/packages"
>> site is for scripts
>
> Uh, ok.
>
>> I have no objections to make a octave_autorebase-001001-1.tar.xz
>> anyway when the new autorebase is in place.
>
> I'm not exactly sure now, but I thought the idea was that the
> PA
Marco Atzeri writes:
> R seems to use
> /usr/lib/R/site-library
> for new add-on stuff.
Right. I'm not sure how common it is for users to use that facility.
> And
> /usr/lib/R/library
> /usr/lib/R/modules
>
> for updating existing stuff already part of the core.
Are you expecting users to
On Jan 24 16:32, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Marco, Achim, Yaakov? Anybody of you here?
> >
> >
> > I mean, hey, how are we going to go forward if nobody even bothers to
> > reply? :(
>
> I just came back from a business trip halfway around the world.
Sorry, but we can't a
50 matches
Mail list logo
