On Dec 8 16:03, Yaakov Selkowitz wrote:
> The attached patch should fix the reported issue with handling of packages
> with -X.Y release numbers.
>
>
> Yaakov
> 2014-12-08 Yaakov Selkowitz
>
> * package_source.cc (packagesource::set_canonical): Fix handling
> of package release
On Dec 8 20:40, Andrew Schulman wrote:
> > > Here's what I have at the moment based on your branch as of a few weeks
> > > ago. However, with password-protected SSH keys, the password prompt
> > > isn't handled properly. Any ideas?
> >
> > Re password prompts: I see the problem. It's because
On Dec 8 15:52, Ken Brown wrote:
> On 12/8/2014 11:48 AM, Achim Gratz wrote:
> >Ken Brown writes:
> >>I'm not convinced that we need to worry so much about all these
> >>details. What if we just check (based on timestamps of files in
> >>/etc/setup/*.lst.gz) whether anything has been installed in
On Dec 8 15:28, Warren Young wrote:
> On Dec 6, 2014, at 9:57 AM, Corinna Vinschen
> wrote:
>
> > Also, can we automate this?
>
> If you’re suggesting an automatic promotion of package to Base, I’d
> argue for the opposite: automatic detection of dependency creep.
>
> I’ve got in mind the 2-3
> On Dec 8 20:40, Andrew Schulman wrote:
> > > > Here's what I have at the moment based on your branch as of a few weeks
> > > > ago. However, with password-protected SSH keys, the password prompt
> > > > isn't handled properly. Any ideas?
> > >
> > > Re password prompts: I see the problem.
On 12/9/2014 5:43 AM, Corinna Vinschen wrote:
On Dec 8 15:52, Ken Brown wrote:
On 12/8/2014 11:48 AM, Achim Gratz wrote:
Ken Brown writes:
I'm not convinced that we need to worry so much about all these
details. What if we just check (based on timestamps of files in
/etc/setup/*.lst.gz) whet
Corinna Vinschen writes:
> I still don't grok why everybody is so hot on keeping the base install
> so very small. Our Base package set is really tiny in comparison
> with any Linux distro. Perl is default on most of them. Why not
> for us? Disk space is dirt cheap these days.
It's more like t
On 2014-12-09 04:34, Corinna Vinschen wrote:
On Dec 8 16:03, Yaakov Selkowitz wrote:
--- package_source.cc 17 Apr 2006 16:13:17 - 2.10
+++ package_source.cc 8 Dec 2014 21:43:15 -
@@ -52,9 +52,9 @@ packagesource::set_canonical (char const
while (bend && (tmp = strchr (bend +
Ken Brown writes:
>>> The attached script is what I had in mind. It's better than what we have
>>> now and could be a starting point.
Looks good. I have cocluded that at the moment we can't restrict the
info update to just the packages touched by the install, mainly because
there's no way to tra
Andrew Schulman writes:
> upload
> Adds the "upload" command: upload finished packages to cygwin.com.
I don't think the !ready files should be created by cygport, at all.
Also, I would rather want to place these files into a local
staging/mirror area first and then upload after the files have b
On Dec 9 10:42, Yaakov Selkowitz wrote:
> On 2014-12-09 04:34, Corinna Vinschen wrote:
> >On Dec 8 16:03, Yaakov Selkowitz wrote:
> >>--- package_source.cc 17 Apr 2006 16:13:17 - 2.10
> >>+++ package_source.cc 8 Dec 2014 21:43:15 -
> >>@@ -52,9 +52,9 @@ packagesource::set
On Dec 9 17:35, Achim Gratz wrote:
> Corinna Vinschen writes:
> > I still don't grok why everybody is so hot on keeping the base install
> > so very small. Our Base package set is really tiny in comparison
> > with any Linux distro. Perl is default on most of them. Why not
> > for us? Disk spa
On 12/9/2014 12:48 PM, Corinna Vinschen wrote:
On Dec 9 17:35, Achim Gratz wrote:
Corinna Vinschen writes:
I still don't grok why everybody is so hot on keeping the base install
so very small. Our Base package set is really tiny in comparison
with any Linux distro. Perl is default on most of
On Dec 9 14:10, Ken Brown wrote:
> On 12/9/2014 12:48 PM, Corinna Vinschen wrote:
> >Come to think of it. When exactly do we want to allow installing
> >packages without also installing the deps? How much sense does
> >this option really have?
>
> I've had occasion to do this when testing/debug
> Andrew Schulman writes:
> > upload
> > Adds the "upload" command: upload finished packages to cygwin.com.
>
> I don't think the !ready files should be created by cygport, at all.
Yaakov will decide, but I disagree. The point of having an upload command
is to relieve packagers of the tedium a
> * The current implementation puts the !ready file into a package-specific
> directory, e.g. /x86_64/screen, instead of /x86_64.
Should say: /x86_64/release/screen, instead of /x86_64/release.
On 12/9/2014 2:52 PM, Corinna Vinschen wrote:
On Dec 9 14:10, Ken Brown wrote:
On 12/9/2014 12:48 PM, Corinna Vinschen wrote:
Come to think of it. When exactly do we want to allow installing
packages without also installing the deps? How much sense does
this option really have?
I've had oc
On 12/9/2014 10:46 PM, Ken Brown wrote:
On 12/9/2014 2:52 PM, Corinna Vinschen wrote:
On Dec 9 14:10, Ken Brown wrote:
On 12/9/2014 12:48 PM, Corinna Vinschen wrote:
Come to think of it. When exactly do we want to allow installing
packages without also installing the deps? How much sense d
On Dec 9, 2014, at 3:48 AM, Corinna Vinschen wrote:
> On Dec 8 15:28, Warren Young wrote:
>>
>> I’ve got in mind the 2-3 times in my memory where Perl has crept into
>> the minimal install set via some indirect dependency.
>
> I still don't grok why everybody is so hot on keeping the base inst
19 matches
Mail list logo