On Tuesday 28 April 2009 23:58, Elan Ruusamäe wrote:
On Tuesday 28 April 2009 19:41, Andrzej Krzysztofowicz wrote:
How to recognize dirs here ?
And: what would we do if we need to create packages named mirrors,
adapter, builder, md5 some day? Is there a simple way to replace a
file by a
On Wednesday 29 of April 2009, Elan Ruusamäe wrote:
On Tuesday 28 April 2009 23:58, Elan Ruusamäe wrote:
On Tuesday 28 April 2009 19:41, Andrzej Krzysztofowicz wrote:
How to recognize dirs here ?
And: what would we do if we need to create packages named mirrors,
adapter, builder,
On Wed, Apr 29, 2009 at 09:17:28 +0200, Arkadiusz Miskiewicz wrote:
drwxr-xr-x 2 cvs cvs 59 2009-04-28 16:11 template-trac-plugin/
drwxr-xr-x 2 cvs cvs 54 2009-04-28 16:11 template-webapp/
It can be merged. Is templates dir fine?
template-specs (in case some 'templates' package emerges
On Wednesday 29 of April 2009, Tomasz Pala wrote:
On Wed, Apr 29, 2009 at 09:17:28 +0200, Arkadiusz Miskiewicz wrote:
drwxr-xr-x 2 cvs cvs 59 2009-04-28 16:11 template-trac-plugin/
drwxr-xr-x 2 cvs cvs 54 2009-04-28 16:11 template-webapp/
It can be merged. Is templates dir fine?
On Wed, Apr 29, 2009 at 01:30:26 +0200, Jan Rekorajski wrote:
discussions. AFAIR switch from flat SPECS/SOURCES to package-per-dir was
agreed on (with some kind of server side symlinked SPECS). The rest was
You remember correctly, there were consensus with flat specs access.
a flame fest,
On Wed, Apr 29, 2009 at 09:28:47 +0200, Arkadiusz Miskiewicz wrote:
On Wednesday 29 of April 2009, Tomasz Pala wrote:
It can be merged. Is templates dir fine?
template-specs (in case some 'templates' package emerges sometime)?
And maybe it should be outside of packages/ leaving this for
On Wednesday 29 of April 2009, Tomasz Pala wrote:
And how about moving scripts (builder, adapter etc.)? It would be
finally possible 'to bring them all and in the darkness bind them'.
I like doing just ../builder -bb whatever or ../pldnotify.awk
package/package.spec but well. Better solutions
On Tue, Apr 28, 2009 at 17:48:20 +0200, Jan Rekorajski wrote:
triggered symlinks on commits like it was done for filling packages/ tree?
We'll do, but I don't know if it won't go away if/when we switch from
Would they be commitable (two-way) or read-only? And when we may expect
this?
Build
On Wed, Apr 29, 2009 at 09:45:44 +0200, Arkadiusz Miskiewicz wrote:
And how about moving scripts (builder, adapter etc.)? It would be
finally possible 'to bring them all and in the darkness bind them'.
I like doing just ../builder -bb whatever or ../pldnotify.awk
package/package.spec but
On Wednesday 29 April 2009 10:46:32 Tomasz Pala wrote:
Build dir in package space is a bad idea, you will end up with searching
through a thousands of directories looking for build leftovers that ate
your disk space. Current layout is IMO just what we need.
I agree, moreover I'd like to
On Wednesday 29 April 2009 10:53:01 Tomasz Pala wrote:
On Wed, Apr 29, 2009 at 09:45:44 +0200, Arkadiusz Miskiewicz wrote:
And how about moving scripts (builder, adapter etc.)? It would be
finally possible 'to bring them all and in the darkness bind them'.
I like doing just ../builder -bb
On Wednesday 29 April 2009 11:17:43 Elan Ruusamäe wrote:
how about (for now) just /packages as files?
nevermind, seems checkout root module respecs CVS/Root and getting them is easy
as:
11:23:35 glen[load: 1@carme-pld ~/rpm/packages$ cvs co template-specs
cvs server: Updating
On Wed, Apr 29, 2009 at 11:17:43 +0300, Elan Ruusamäe wrote:
how about (for now) just /packages as files? as it would be easier to locate
them (builder --init-rpm-dir would checkout them for you)
All the scripts already reside in /packages and they are difficult to
locate without builder
Dnia środa, 29 kwietnia 2009, Tomasz Pala napisał:
Would they be commitable (two-way) or read-only? And when we may expect
this?
read-only. It's a almost guaranteed that after switching VCS-es, there would
be no real possibility of doing them +rw.
--mmazur
On Wednesday 29 April 2009 11:54:26 Tomasz Pala wrote:
But it's more difficult to get new package now (having Entries.Static):
solved now (cvs up builder)
before:
~/rpm/SPECS: cvs up icewm.spec
now:
~/rpm/packages: cvs up icewm- no effect
~/rpm/packages: cvs up
On Wednesday 29 April 2009 11:48:12 Mariusz Mazur wrote:
Dnia środa, 29 kwietnia 2009, Tomasz Pala napisał:
Would they be commitable (two-way) or read-only? And when we may expect
this?
read-only. It's a almost guaranteed that after switching VCS-es, there
would be no real possibility of
On Wednesday 29 of April 2009, Elan Ruusamäe wrote:
On Wednesday 29 April 2009 11:48:12 Mariusz Mazur wrote:
Dnia środa, 29 kwietnia 2009, Tomasz Pala napisał:
Would they be commitable (two-way) or read-only? And when we may expect
this?
read-only. It's a almost guaranteed that after
Tomasz Pala wrote:
On Wed, Apr 29, 2009 at 09:28:47 +0200, Arkadiusz Miskiewicz wrote:
On Wednesday 29 of April 2009, Tomasz Pala wrote:
It can be merged. Is templates dir fine?
template-specs (in case some 'templates' package emerges sometime)?
And maybe it should be outside
I just did a server-side read-only SPECS that's full of symlinks to
the ../packages spec files. I've also added a small monitoring script that
will rename/delete/create new symlinks whenever a directory in packages/ gets
created/deleted/renamed.
Enjoy.
--mmazur
Oh, and I'll use this mail as
Dnia środa, 29 kwietnia 2009, Elan Ruusamäe napisał:
plz +rw in cvs mode, as i tend to be mentor fixing silly mistakes others
commit to specs, checkout each package to fix those will suck
Nope. Even the possibility of RW will go away soon, so you should stop relying
on it right about now.
On Wednesday 29 April 2009 13:55:40 Mariusz Mazur wrote:
I just did a server-side read-only SPECS that's full of symlinks to
the ../packages spec files.
doing cvs up revealed what other non-spec files were present, where they are
now?
g...@builder-ac pld/SPECS $ grep 'is no longer' /tmp/ss
Dnia środa, 29 kwietnia 2009, Elan Ruusamäe napisał:
On Wednesday 29 April 2009 13:55:40 Mariusz Mazur wrote:
I just did a server-side read-only SPECS that's full of symlinks to
the ../packages spec files.
doing cvs up revealed what other non-spec files were present, where they
are now?
On Wednesday 29 April 2009 14:13:03 Mariusz Mazur wrote:
Dnia środa, 29 kwietnia 2009, Elan Ruusamäe napisał:
On Wednesday 29 April 2009 13:55:40 Mariusz Mazur wrote:
I just did a server-side read-only SPECS that's full of symlinks to
the ../packages spec files.
doing cvs up revealed
Dnia środa, 29 kwietnia 2009, Mariusz Mazur napisał:
Dnia środa, 29 kwietnia 2009, Elan Ruusamäe napisał:
plz +rw in cvs mode, as i tend to be mentor fixing silly mistakes others
commit to specs, checkout each package to fix those will suck
Nope. Even the possibility of RW will go away
Dnia środa, 29 kwietnia 2009, Elan Ruusamäe napisał:
if it's not big secret, then what is the new place?
packages/builder, just don't tell anyone :)
--mmazur
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
On Wednesday 29 April 2009 14:23:50 Mariusz Mazur wrote:
Dnia środa, 29 kwietnia 2009, Elan Ruusamäe napisał:
if it's not big secret, then what is the new place?
packages/builder, just don't tell anyone :)
no, i mean the _other_ files in that list...
On Wed, Apr 29, 2009 at 12:49:23 +0300, Elan Ruusamäe wrote:
~/rpm/packages: cvs up icewm- no effect
~/rpm/packages: cvs up icewm/icewm.spec - error
cvs [update aborted]: no such directory `icewm'
~/rpm/packages: cvs co icewm/icewm.spec - error
cvs server: cannot find module
Dnia środa, 29 kwietnia 2009, Elan Ruusamäe napisał:
packages/builder, just don't tell anyone :)
no, i mean the _other_ files in that list...
http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2009-April/021049
.html
Dunno. If some of them are still useful, just copy them from
On Wednesday 29 April 2009 14:36:44 Tomasz Pala wrote:
On Wed, Apr 29, 2009 at 12:49:23 +0300, Elan Ruusamäe wrote:
~/rpm/packages: cvs up icewm- no effect
~/rpm/packages: cvs up icewm/icewm.spec - error
cvs [update aborted]: no such directory `icewm'
~/rpm/packages: cvs co
Are there any objections against adding R: vim-rt-extras to gvim-gtk?
Without vim-rt-extras installed I get warning:
Error detected while processing /usr/share/vim/vim72/menu.vim:
line 155:
E121: Undefined variable: paste#paste_cmd
E15: Invalid expression: 'vnoremenu script Edit.PasteTab+gP^I' .
On Wednesday 29 April 2009 11:12:36 Elan Ruusamäe wrote:
On Wednesday 29 April 2009 10:46:32 Tomasz Pala wrote:
Build dir in package space is a bad idea, you will end up with
searching through a thousands of directories looking for build
leftovers that ate your disk space. Current layout
On Wed, Apr 29, 2009 at 16:13:06 +0300, Elan Ruusamäe wrote:
Thnx (however this fetches all package contents, any way to get spec
alone?)
./builder -g -ns icewm?
Works as expected, thanks.
--
Tomasz Pala go...@pld-linux.org
___
pld-devel-en
32 matches
Mail list logo
