Mailinglist Archive: opensuse-buildservice (233 mails)
| < Previous | Next > |
[opensuse-buildservice] BuildService and the :
- From: Dirk Stoecker <opensuse@xxxxxxxxxxxx>
- Date: Thu, 10 May 2007 08:41:41 +0200 (CEST)
- Message-id: <Pine.LNX.4.64.0705100826500.26066@xxxxxxxxxxxxxxxxx>
Hello,
I asked myself, why the buildservice uses the ":" as seperation
character? This makes some trouble in commandline, as : must always be
escaped and also it looks strange from users side.
Wouldn't it be better to introduce "/" in it's full meaning?
The repositories are already stored hierarchical on the download servers.
Having the same in the buildservice would be nice. E.G. my
home:dstoecker:perl would be nice to have as link perl in home:dstoecker.
(or better home/dstoecker/perl).
I know that would probably be a bigger change right now, but it would make
the buildservice compatible to the general Unix path conventions.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
I asked myself, why the buildservice uses the ":" as seperation
character? This makes some trouble in commandline, as : must always be
escaped and also it looks strange from users side.
Wouldn't it be better to introduce "/" in it's full meaning?
The repositories are already stored hierarchical on the download servers.
Having the same in the buildservice would be nice. E.G. my
home:dstoecker:perl would be nice to have as link perl in home:dstoecker.
(or better home/dstoecker/perl).
I know that would probably be a bigger change right now, but it would make
the buildservice compatible to the general Unix path conventions.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |