| 1 |
On 20/9/2005 7:37:19, Georgi Georgiev (chutz@×××.net) wrote: |
| 2 |
> maillog: 20/09/2005-07:21:08(+0200): Christian Parpart types |
| 3 |
> > On Monday 19 September 2005 15:22, warnera6 wrote: |
| 4 |
> > > Mark Loeser wrote: |
| 5 |
> > > > Paul de Vrieze wrote: |
| 6 |
> > > >> I think that dev-util is a very specific category containing |
| 7 |
> > > >> development utilities of some sort. There might be some |
| 8 |
> > > >> misclassifications in them, but from a user perspective I don't |
| 9 |
> > > >> really care about the language anything is written in. As C++ is so |
| 10 |
> > > >> widespread I don't think that anything but app-misc or the like |
| 11 |
> > > >> should be moved into a dev-cpp category. |
| 12 |
> > > > |
| 13 |
> > > > This isn't for what the package is written in, but more for what the |
| 14 |
> > > > package is for. If the package is a utility for use when doing |
| 15 |
> > > > coding with C++, like the ones I listed, then I think it should be |
| 16 |
> > > > in dev-cpp. That's what the metadata for the category describes it |
| 17 |
> > > >to be. |
| 18 |
> > > > Mark |
| 19 |
> > > |
| 20 |
> > > Once again I'd like to point out that organizing packages in the tree |
| 21 |
> > > by category is a stupid idea for this very reason. |
| 22 |
> > |
| 23 |
> > and what's *your* certain proposal then? |
| 24 |
> |
| 25 |
> That's been discussed a number of times already. The best idea is to |
| 26 |
> leave the categories alone and forget that the category means anything. |
| 27 |
> Or, to throw the ball back in your court, could *you* suggest |
| 28 |
> alternatives that accomplish the following: |
| 29 |
> |
| 30 |
> (quoting [1]:) |
| 31 |
> |
| 32 |
> More precisely, what I'd like to see, in order of preference, is |
| 33 |
> |
| 34 |
> - that package in my overlay that has net-wireless/gnome-phone-manager |
| 35 |
> in its *DEPENDs to work for as long as needed |
| 36 |
> - the net-wireless/gnome-phone-manager that I have in my overlay to work |
| 37 |
> for as long as needed |
| 38 |
> - my net-wireless/gnome-phone-manager binary packages to work without |
| 39 |
> having to be "fixpackage"d |
| 40 |
> - the location of the ebuilds for net-wireless/gnome-phone-manager to |
| 41 |
> stay in the same physical path on my filesystem |
| 42 |
> |
| 43 |
> end quote |
| 44 |
> I would grade the above features as "vital", "badly needed", "happy to |
| 45 |
> see it done", "cosmetic". I.e., even solving only the first one is |
| 46 |
> enough, though if you could get to number two it would be better. |
| 47 |
|
| 48 |
|
| 49 |
Here's another requirement I'd like to add to the list: |
| 50 |
|
| 51 |
- when moving stuff around, change history moves too |
| 52 |
|
| 53 |
CVS doesn't support this, but subversion does (along with atomic commits, |
| 54 |
also useful to ensure integrity of the tree during a move). The support |
| 55 |
for symlinks in subversion may also provide a way to resolve the overlay |
| 56 |
problem... |
| 57 |
|
| 58 |
-- |
| 59 |
gentoo-dev@g.o mailing list |
Archives